Skip to main content
Glama

Update Test Case

update_test_case

Update an existing test case in QA Sphere. Modify optional fields like title, priority, steps, or tags; omitted fields retain current values.

Instructions

Update an existing test case in QA Sphere. Only users with role User or higher are allowed to update test cases. Optional fields can be omitted to keep the current value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoList of tag titles
linksNoAdditional links relevant to the test case
stepsNoList of test case steps
titleNoTest case title. In template test cases, may contain `${var}` placeholders that are substituted via `parameterValues` to produce filled test case titles.
commentNoTest case precondition (HTML format). DEPRECATED — prefer the `precondition` object
isDraftNoTo publish a draft test case. A published test case cannot be converted to draft
priorityNoTest case priority
projectCodeYesProject code identifier (e.g., BDI)
customFieldsNoCustom field values to update. Only the specified keys are modified; others remain unchanged.
preconditionNoTest case precondition: either `{sharedPreconditionId}` to reference a shared one, or `{text}` for a standalone precondition
requirementsNoTest case requirements
parameterValuesNoFull replacement of the template test case parameter values. Applies only when the target is a template test case: entries with `tcaseId` update the corresponding filled test case; entries without `tcaseId` generate a new one; any existing filled test case whose `tcaseId` is not present in this array will be deleted. To preserve existing filled test cases while appending, include their current `{tcaseId, values}` pairs.
tcaseOrLegacyIdYesTest case identifier (can be one of test case UUID, sequence or legacy ID). Note: when the target is a `filled` test case, only `priority` can be updated directly; to change other fields, update the parent template or use `parameterValues`.
filledTCaseTitleSuffixParamsNoParameter names whose substituted values are appended to each filled test case title for disambiguation (e.g., pass `["env"]` to suffix titles with the `env` value). Applies only to template test cases.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesSuccess message
Behavior3/5

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

With no annotations, description discloses authorization and optional field behavior, but lacks detail on side effects (e.g., template test case parameter handling). Adequate but not rich.

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 sentences, front-loaded with purpose, no wasted words.

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

Completeness2/5

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

Complex tool (14 params, nested objects) but description is simplistic; lacks guidance on template test cases, parameterValues, and return value.

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?

100% schema coverage means schema does heavy lifting; description adds minimal extra meaning beyond restating that optional fields can be omitted.

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?

Clearly states the verb ('update') and resource ('existing test case in QA Sphere'), and distinguishes from siblings like create_test_case.

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?

Provides role-based usage constraint and mentions optional field behavior, but no explicit when-not or alternatives beyond implied context.

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/Hypersequent/qasphere-mcp'

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