Skip to main content
Glama
bun913

TestRail MCP Server

by bun913

getCases

Retrieve a list of test cases with basic fields from a TestRail project and suite. Filter by creator, priority, milestone, and more to find specific cases.

Instructions

Retrieves test cases list with basic fields only (excludes steps/expected results for performance). REQUIRED: projectId, suiteId. OPTIONAL: createdBy, filter, limit (default 50), milestoneId, offset (default 0), priorityId, refs, sectionId, templateId, typeId, updatedBy, labelId. Use getCase for full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesTestRail Project ID
suiteIdYesTestRail Suite ID
createdByNoA comma-separated list of creators (user IDs) to filter by
filterNoOnly return cases with matching filter string in the case title
limitNoThe number of test cases the response should return (The response size is 50 by default) —requires TestRail 6.7 or later
milestoneIdNoA comma-separated list of milestone IDs to filter by (not available if the milestone field is disabled for the project)
offsetNoWhere to start counting the tests cases from (the offset)—requires TestRail 6.7 or later
priorityIdNoA comma-separated list of priority IDs to filter by
refsNoA single Reference ID (e.g. TR-1, 4291, etc.) —requires TestRail 6.5.2 or later
sectionIdNoThe ID of a test case section
templateIdNoA comma-separated list of template IDs to filter by —requires TestRail 5.2 or later
typeIdNoA comma-separated list of case type IDs to filter by
updatedByNoA comma-separated list of user IDs who updated test cases to filter by
labelIdNoA comma-separated list of label IDs to filter by
Behavior4/5

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

Description discloses that only basic fields are returned for performance and provides default values for limit and offset. However, it does not mention error handling or version requirements for some parameters (though those are in schema). Without annotations, this is fairly transparent.

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

Conciseness5/5

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

Two concise sentences plus a clear list. Front-loaded with the most important information. No superfluous content.

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

Completeness4/5

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

Given no output schema, description explains the output is basic fields for performance, but does not specify which fields are included or mention pagination structure. Still fairly complete for a list retrieval tool.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. Description groups parameters into REQUIRED/OPTIONAL but adds little detail beyond schema descriptions. It does provide a high-level overview of parameter roles.

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?

Description uses specific verb 'Retrieves' and resource 'test cases list', and distinguishes from sibling getCase by noting it excludes steps/expected results for performance.

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?

Clearly states REQUIRED parameters (projectId, suiteId) and lists OPTIONAL parameters. Provides explicit alternative: 'Use getCase for full details' for when full details are needed.

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

Install Server

Other Tools

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/bun913/mcp-testrail'

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