Retrieve tests for a specific TestRail run by run ID. Use pagination to access all tests in manageable pages.
Retrieves a list of tests for a test run / テスト実行に含まれるテスト一覧を取得します
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of tests to return per page. If you cannot get all tests, try separating the request into multiple calls | |
| runId | Yes | TestRail Run ID | |
| offset | No | Offset for pagination |
Changes observed during successful MCP inspections.
v0.19.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description does not disclose any behavioral traits (e.g., read-only nature, authorization, rate limits). Minimal info beyond the basic retrieval action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Short and front-loaded, with bilingual text. No wasted words, though could be slightly expanded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, and description doesn't explain return values or pagination details. Adequate for a basic list tool, but missing some context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters with descriptions (limit, offset, runId). The tool description adds no extra meaning, so baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a list of tests for a test run, specifying the resource and scope. It distinguishes from siblings like getTest (singular) and getResultsForRun.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives like getTest or getResultsForRun. Also lacks context on pagination usage despite parameter documentation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.