Skip to main content
Glama

get_execution_cases

Read-onlyIdempotent

List case-run rows of a manual test execution to inspect statuses and prepare per-case result reporting. Returns executionCaseId, case details, status, and step outcomes.

Instructions

List the individual case-run rows of a Manual Test Execution so you can report results against them. Returns each row with executionCaseId (a UUID, and the value report_case_result takes), caseId, caseNumber, title, group and groupId, sourceType, current status, the case-level result fields (notes, causedBy, durationMinutes, executedBy, executedAt), parentCases, the externalLinks of the case (Jira or Linear tickets, present only if you also hold integrations:read), and steps (0-based index, action, expected, current step status, issueDescription). groupId is the one to keep: it is what report_case_result wants when the same case sits in more than one source group, while group is only that group name. sourceType says whether the group came from a suite, a Test Collection or a bare set of cases. Note that the title field is called title here while get_case_execution_history calls the same thing caseTitle. caseId is null on rows whose underlying case has been deleted, so target those by executionCaseId, which is always present. executedBy here is the internal user UUID of whoever last recorded a result, not a name, and nothing on this surface resolves a user UUID - get_case_execution_history returns that same field for the same rows as an EMAIL ADDRESS, so call that one when you need to say who. It can be null even where executedAt is set, on seeded or imported results, and it records who last WROTE a result rather than who owns the case: a case row carries no assignee at all. durationMinutes is written only by report_case_result and has no control in the UI, so it is null on most rows. Everything report_case_result writes reads back here. Use after add_suites_to_execution, add_collections_to_execution or add_cases_to_execution, and before report_case_result. Supports paging and filtering by group, status or title.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
searchNoOptional case-title search
statusNoOptional case-status filter (e.g. not_executed, passed, failed)
groupIdNoOptional: only cases in this source group (execution_test_run UUID)
executionIdYesExecution UUID

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.5.0

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint and idempotentHint are true, and the description goes well beyond that: it explains nullability of caseId and durationMinutes, the UUID-vs-email executionBy discrepancy, conditional externalLinks based on integrations:read scope, and that report_case_result writes are visible here. This gives an agent a strong behavioral model of the tool without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense, but nearly every sentence carries actionable information about return fields, nullability, or caveats. It is not a model of brevity, but because there is no output schema, the field-level detail is justified and the core workflow guidance is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing endpoint with no output schema, the description covers the returned fields, their types/nullability, permissions, workflow placement, and how this tool differs from get_case_execution_history. No important usage dimension appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents search, status, groupId, and executionId, while limit and offset rely on defaults and bounds rather than descriptive text. The description compensates by explaining that pagination and filtering by group/status/title are supported and by establishing groupId as the significant identifier for report_case_result, which is exactly the kind of semantic weight an agent needs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with a specific verb and resource: 'List the individual case-run rows of a Manual Test Execution' and adds a clear purpose ('so you can report results against them'). It also distinguishes itself from get_case_execution_history by pointing out the title field naming difference and the user UUID vs email difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states where this tool fits in a workflow: use it after add_suites_to_execution, add_collections_to_execution, or add_cases_to_execution, and before report_case_result. It also directs the agent to get_case_execution_history when a user UUID needs to be resolved to an email address, giving a clear alternative-selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/m00nreport/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server