Retrieve a paginated list of tests for a given TestRail run ID.
Retrieves a list of tests for a test run / テスト実行に含まれるテスト一覧を取得します
| Name | Required | Description | Default |
|---|---|---|---|
| runId | Yes | TestRail Run ID | |
| limit | No | Number of tests to return per page. If you cannot get all tests, try separating the request into multiple calls | |
| offset | No | Offset for pagination |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It only states it retrieves tests but does not disclose pagination behavior or any side effects. Minimal transparency.
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?
Very concise (one sentence), but includes redundant Japanese text. Lacks structured sections to aid quick scanning.
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?
Description is minimal for a list-retrieval tool with 3 parameters and no output schema. Missing details about response format, pagination, and error handling.
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?
Input schema covers all parameters with descriptions. Description adds no extra meaning beyond schema. Baseline 3 as schema is self-sufficient.
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?
Description clearly states verb 'Retrieves' and resource 'list of tests for a test run'. 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 versus alternatives like getResultsForRun or getTest. No mention of prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bun913/mcp-testrail'
If you have feedback or need assistance with the MCP directory API, please join our Discord server