Skip to main content
Glama
bun913

TestRail MCP Server

by bun913

updateCases

Update multiple test cases at once by setting common field values such as title, type, priority, or custom fields. Streamline bulk modifications in TestRail.

Instructions

Updates multiple test cases simultaneously with the same field values / 複数のテストケースを同じフィールド値で一括更新します. NOTE: templateId=2 is required to use customStepsSeparated (array of step objects with 'content' and 'expected' fields). For simple text steps, use customSteps and customExpected instead. Use customFields for any additional custom fields (e.g., {custom_case_security_score: 'high'}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesTestRail Project ID
suiteIdYesTestRail Suite ID
caseIdsYesArray of TestRail Case IDs
titleNoTest case title
typeIdNoTest case type ID
priorityIdNoTest case priority ID
estimateNoTest case estimated time
milestoneIdNoTestRail Milestone ID
refsNoTest case references
templateIdNoTemplate ID (use 2 for custom_steps_separated support)
customPrerequisitesNoPrerequisites
customStepsNoTest case steps
customExpectedNoExpected results
customStepsSeparatedNoSeparated test steps array (requires template_id=2)
customFieldsNoAdditional custom fields as key-value pairs (e.g., {custom_case_security_score: 'high'})
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It explains the template and field relationships but omits important details like whether unspecified fields are overwritten or preserved, and no mention of auth or rate limits.

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 a single sentence plus a note, efficient and front-loaded. The bilingual text adds minor redundancy but does not detract from clarity.

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

Completeness3/5

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

Despite many parameters and no output schema, the description covers key relationships. However, it lacks guidance on common parameter combinations and does not position itself among sibling tools, leaving some gaps for an AI agent.

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?

Schema coverage is 100%, baseline 3. The description adds value by explaining the required template for customStepsSeparated and providing an example for customFields, which goes beyond the schema definitions.

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 clearly states it updates multiple test cases with identical field values, using a specific verb and resource. The distinction from sibling tools like updateCase is implied through the plural 'cases' in the name and description.

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

Usage Guidelines4/5

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

The description provides context for using customStepsSeparated with templateId=2 and distinguishes between step formats. However, it does not explicitly state when to use this tool versus alternatives like updateCase or addCase.

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