Skip to main content
Glama
bun913

TestRail MCP Server

by bun913

updateCases

Batch update multiple test cases in TestRail with common field values such as title, priority, and custom fields.

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'})

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.6
  2. Removedv0.12.1
  3. First observedv0.19.2

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as atomicity, error handling, or permissions needed. It only states 'updates' without detailing consequences or side effects for batch operations.

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 front-loaded with the main action and includes a useful note. It is slightly longer due to bilingual text, but each sentence adds value. Could be more concise but still effective.

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?

Given 15 parameters and no output schema, the description addresses the templateId nuance but lacks details on return values, error handling, or batch behavior. It provides enough context for basic usage but is incomplete for a complex operation.

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%, but the description adds extra meaning beyond the schema by explaining the relationship between templateId and customStepsSeparated, and how customFields should be structured. This provides practical usage context.

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 the tool updates multiple test cases simultaneously with the same field values, distinguishing it from updateCase (singular) and other case operations. The bilingual text reinforces the purpose.

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 specific guidance on using templateId=2 for customStepsSeparated, and advises using customSteps/customExpected or customFields for different scenarios. However, it does not explicitly contrast with sibling tools or state when to use this tool versus alternatives like updateCase.

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