Skip to main content
Glama

update_manual_test_case

Update an existing manual test case by modifying fields like steps, status, priority, and linking Jira issues.

Instructions

Update an existing manual test case. Use this to modify test case details, steps, status, priority, or any other fields. Provide only the fields you want to update in the updates object. To add comments, pass updates.comments as an array of strings — each becomes a new comment (PAT owner is author). To link Jira issues, pass updates.issues as an array of ticket keys (e.g. ['PROJ-123']); the server looks each up in the project's connected Jira and saves with title+url, or as a plain text stub when Jira isn't connected or the ticket isn't found (same fallback as the UI).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseIdYesTest case ID (Required). Can be internal _id or human-readable ID like 'TC-123'.
updatesYesObject containing the fields to update. Can include: name, description, steps, status, priority, severity, type, layer, behavior, preconditions, postconditions, automationStatus, tags, flags, attachments, customFields, etc.
projectIdYesProject ID (Required). The TestDino project identifier.
Behavior4/5

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

With no annotations provided, the description carries full responsibility. It discloses behavioral traits: comments are appended, PAT owner is author, Jira linking has fallback behavior, and duplicate issues are skipped. It does not explicitly state whether non-updated fields remain unchanged, but this is implied.

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 paragraph but front-loads the purpose. It is concise enough, though slightly longer than necessary. Could benefit from bullet points for readability.

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 the complexity of the tool (nested updates object) and absence of output schema, the description covers the main input behaviors well. It does not mention error handling or permissions, but for a typical update operation this is sufficient.

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 significant meaning beyond the schema for the 'comments' and 'issues' parameters, explaining their behavior in detail. This goes beyond a baseline of 3.

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 'Update an existing manual test case' and lists the types of fields that can be modified. It distinguishes from sibling tools like 'create_manual_test_case' by focusing on modification rather than creation.

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 clear instructions: 'Provide only the fields you want to update in the updates object' and explains how to add comments and link Jira issues. However, it does not explicitly state when not to use this tool or compare it with other update tools like 'update_manual_run'.

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/testdino-hq/testdino-mcp'

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