Skip to main content
Glama

Update Test Case In A Run

update_run_test_case
Destructive

Update a test case in a manual run by setting assignee or pass/fail verdict, or recording a detailed result with comments, linked issues, and step results.

Instructions

Update one test case inside a manual run. Two modes, same tool: (1) Quick verdict — pass updates.assigneeUserId and/or updates.result/status to do what clicking "Assign to" and the result pill does in the UI. (2) Detailed result — additionally pass any of updates.comment (rich HTML), updates.linkedIssues, updates.stepResults to record a full result entry, exactly like the UI's "Add detailed result…" dialog. Whenever any of those rich fields are present the server logs a complete result instead of a bare status change. NOTE: combining updates.assigneeUserId with any detailed-result field in one call is rejected — make two calls (one to assign, one to record the result), mirroring the UI's separate "Assign to" and "Add detailed result…" actions. Requires write permission. rtcRef accepts the caseKey ("TC-156"), the internal tcm_rtc_... RTC ID, or the underlying test case _id. Works for both already-touched cases and "untested" virtual cases (the server auto-creates the per-case record on first edit). Closed runs reject result writes. IMPORTANT: send updates.assigneeUserId as an email OR User _id — both are accepted. updates.result accepts the UI labels — the canonical values are "untested", "passed", "failed", "blocked", "skipped", "retest". Pass display ("Passed", "Blocked") or canonical ("passed", "blocked") form — the server normalizes lowercase+underscored. To update multiple cases at once, call this tool in parallel (one call per case). Files cannot be added to a result over MCP — tell the user to use the TestDino UI.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "runId": "<runId>",
      "rtcRef": "<rtcRef>",
      "updates": "<updates>"
    },
    "name": "update_run_test_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesInternal run _id or counter-style ID e.g. "RUN-12"
rtcRefYesPer-case record reference — `tcm_rtc_...` _id, caseKey ("TC-156"), or underlying test case _id.
updatesYesQuick verdict: assigneeUserId (email or _id; null to unassign), result/status (display or canonical), elapsed (seconds). Detailed result (any of these triggers a full result entry): comment (rich HTML), linkedIssues (array of linked-issue objects), stepResults (array, e.g. [{ "order": 1, "status": "passed", "comment": "" }]), configuration (the browser/platform this result is for). configuration is REQUIRED when the run covers more than one browser — a result naming none belongs to no cell and is rejected.
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.3
    • changedInput schema / properties / updates / description
      Previous value: -"Quick verdict: assigneeUserId (email or _id; null to unassign), result/status (display or canonical), elapsed (seconds). Detailed result (any of these triggers a full result entry): comment (rich HTML), linkedIssues (array of linked-issue objects), attachments (array of attachment objects/URLs), stepResults (array, e.g. [{ \"order\": 1, \"status\": \"passed\", \"comment\": \"\" }]), configuration (the browser/platform this result is for). configuration is REQUIRED when the run covers more than one browser — a result naming none belongs to no cell and is rejected."New value: +"Quick verdict: assigneeUserId (email or _id; null to unassign), result/status (display or canonical), elapsed (seconds). Detailed result (any of these triggers a full result entry): comment (rich HTML), linkedIssues (array of linked-issue objects), stepResults (array, e.g. [{ \"order\": 1, \"status\": \"passed\", \"comment\": \"\" }]), configuration (the browser/platform this result is for). configuration is REQUIRED when the run covers more than one browser — a result naming none belongs to no cell and is rejected."
  2. Changed7 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (required)."New value: +"Project ID"
    • changedInput schema / properties / rtcRef / description
      Previous value: -"Per-case record reference — `tcm_rtc_...` _id, caseKey ('TC-156'), or underlying test case _id (required)."New value: +"Per-case record reference — `tcm_rtc_...` _id, caseKey (\"TC-156\"), or underlying test case _id."
    • changedInput schema / properties / runId / description
      Previous value: -"Internal run _id or counter-style ID e.g. 'RUN-12' (required)."New value: +"Internal run _id or counter-style ID e.g. \"RUN-12\""
    • addedInput schema / properties / updates / additionalProperties
      Added value: +{}
    • changedInput schema / properties / updates / description
      Previous value: -"Fields to update. Quick verdict fields: assigneeUserId (email or _id, pass null to unassign), result/status (display or canonical form), elapsed (seconds). Detailed-mode fields: comment (HTML), linkedIssues, attachments, stepResults (e.g. [{order, status, comment}]). Quick and detailed are mutually exclusive — mixing an assignee with detailed fields is rejected server-side."New value: +"Quick verdict: assigneeUserId (email or _id; null to unassign), result/status (display or canonical), elapsed (seconds). Detailed result (any of these triggers a full result entry): comment (rich HTML), linkedIssues (array of linked-issue objects), attachments (array of attachment objects/URLs), stepResults (array, e.g. [{ \"order\": 1, \"status\": \"passed\", \"comment\": \"\" }]), configuration (the browser/platform this result is for). configuration is REQUIRED when the run covers more than one browser — a result naming none belongs to no cell and is rejected."
  3. Changed1 schema field changedv2.0.2
    • changedInput schema / properties / updates / description
      Previous value: -"Fields to update: assigneeUserId (email or _id, pass null to unassign), result/status (display or canonical form), elapsed (seconds)."New value: +"Fields to update. Quick verdict fields: assigneeUserId (email or _id, pass null to unassign), result/status (display or canonical form), elapsed (seconds). Detailed-mode fields: comment (HTML), linkedIssues, attachments, stepResults (e.g. [{order, status, comment}]). Quick and detailed are mutually exclusive — mixing an assignee with detailed fields is rejected server-side."
  4. Addedv1.0.10

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, but the description goes well beyond them: it discloses the write-permission requirement, that closed runs reject result writes, that untested virtual cases are auto-created on first edit, that the server normalizes case and display forms, and which field combinations are rejected. It stops short of saying what happens to any pre-existing result fields when a new detailed result is logged.

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?

Front-loaded with the tool's purpose and the mode split, then proceeds through constraints in descending order of importance. Some of the tail repeats the schema verbatim (the rtcRef accepted forms, the assigneeUserId email/_id note), which is wasted space at 100% schema coverage, but the bulk is dense and earns its place.

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?

For a four-parameter mutation tool with a free-form nested `updates` object and no output schema, the description covers modes, validation, permissions, and edge cases well. It omits any statement about return content and leaves the `configuration` cross-browser requirement entirely to the schema, which is the main remaining hole.

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%, so the baseline is 3, but the description adds real meaning: the accepted rtcRef forms with a concrete example ("TC-156", tcm_rtc_..._id), the canonical result value list ("untested" through "retest") which is absent from the schema's otherwise enum-less shape, and the display-vs-canonical normalization rule. That is genuine compensating value for a key nested parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Update one test case inside a manual run") and immediately separates the two operating modes (quick verdict vs detailed result). It does not name its closest siblings (update_manual_test_case, update_manual_run, assign_test), so an agent must infer the boundary from scope alone rather than being routed explicitly.

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?

Very strong on-mode guidance: it explains the two modes, names which fields trigger each, warns that assigneeUserId cannot be combined with detailed-result fields, and prescribes two sequential calls instead. It also says to call in parallel for multiple cases and that files cannot be added over MCP. The only gap is that it never states when to prefer a sibling tool such as update_manual_test_case or assign_test.

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