Skip to main content
Glama

Update Test Case

update_test_case
DestructiveIdempotent

Update an existing test case in Allure TestOps with partial field updates. Replace steps, attachments, tags, issues, or custom fields while preserving omitted values. Requires confirmation to proceed.

Instructions

Update an existing test case in Allure TestOps. ⚠️ CAUTION: Destructive.

Performs a partial update: only supplied fields are sent to the API. When provided, steps replace all existing steps, and attachments replace all existing global attachments. Omit a field to preserve its current value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name for the test case
tagsNoNew list of tags
linksNoNew list of external links. Each dict has 'name', 'url', and optional 'type'.
stepsNoNew list of steps. Each step is a dict with 'action', 'expected', and optional 'attachments' list.
issuesNoList of issue keys to ADD (e.g. ['PROJ-123']).
confirmNoMust be set to True to proceed with update. Safety measure.
automatedNoSet whether the test case is automated
status_idNoID of the test case status
project_idNoOptional override for the default Project ID.
attachmentsNoNew list of global attachments. Each dict has 'name' and 'content' (base64) or 'url'.
descriptionNoNew description
workflow_idNoID of the workflow
clear_issuesNoIf True, remove ALL issues from the test case.
preconditionNoNew precondition
test_case_idYesThe ID of the test case to update
custom_fieldsNoDictionary of custom fields to update (Name -> Value or list of values)
output_formatNoOutput format: 'json' (default) or 'plain'.
remove_issuesNoList of issue keys to REMOVE.
test_layer_idNoID of the test layer
integration_idNoOptional integration ID for issue linking (use list_integrations to find IDs). Required when multiple integrations exist and adding issues. Mutually exclusive with integration_name.
expected_resultNoGlobal expected result for the test case
test_layer_nameNoName of the test layer
integration_nameNoOptional integration name for issue linking (exact case-sensitive match). Required when multiple integrations exist and adding issues. Mutually exclusive with integration_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
nameNo
actionNoRequested operation name.
changesNo
summaryNo
test_case_idNo
requires_confirmationNo
Behavior5/5

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

Adds value beyond annotations by explaining destructive nature, partial update, and that steps/attachments replace existing ones. No contradiction with annotations.

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?

Short and focused: states purpose, caution, and key behaviors in a few lines. No extraneous information.

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

Completeness5/5

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

Given output schema exists, description covers all necessary aspects: partial update, destructive, idempotent, and replacement semantics. Complete for a complex tool.

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). Description adds context about partial update behavior and confirms safety measure, going beyond schema descriptions.

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 clearly states 'Update an existing test case in Allure TestOps' with a specific verb and resource. It distinguishes from siblings like create_test_case and delete_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 guidance on partial update behavior and when to omit fields to preserve values. Implicitly differentiates from create/delete but does not explicitly list alternative tools.

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/ivanostanin/lucius-mcp'

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