Skip to main content
Glama

Update Manual Test Run

update_manual_run
Destructive

Modify fields of an existing manual test run or permanently close it by sending only the changed fields; closing freezes the run and cannot be reopened.

Instructions

Modify an existing manual test run, or close it. Closing is permanent: send updates.status="closed" only when the user asks to close the run, never as part of another edit. Send only fields you want to change inside the updates object. Requires write permission. Allowed fields: name, note, environment, releaseId, state, forecast, tags, linkedIssues, links, selectionMode. Closing works like the UI "Close run" button: it freezes the run, snapshots remaining cases and snaps state to the project's "Done" option; MCP cannot reopen it. Closed runs are read-only except for releaseId (so a run can be re-attached to a different release). Files cannot be added over MCP — tell the user to use the TestDino UI. IMPORTANT: updates.tags must be a JSON array of strings — e.g. ["smoke","regression"] — NOT a comma-separated string.

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>",
      "updates": "<updates>"
    },
    "name": "update_manual_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesInternal _id or counter-style ID
updatesYesFields to update: name, note, environment, releaseId, state, forecast, tags, linkedIssues, links, selectionMode. status="closed" closes the run.
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.3
    • changedInput schema / properties / updates / description
      Previous value: -"Fields to update: name, note, environment, releaseId, state, forecast, tags, linkedIssues, attachments, links, selectionMode. status=\"closed\" closes the run."New value: +"Fields to update: name, note, environment, releaseId, state, forecast, tags, linkedIssues, links, selectionMode. status=\"closed\" closes the run."
  2. Changed6 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 / runId / description
      Previous value: -"Internal _id or counter-style ID (required)."New value: +"Internal _id or counter-style ID"
    • addedInput schema / properties / updates / additionalProperties
      Added value: +{}
    • changedInput schema / properties / updates / description
      Previous value: -"Fields to update: name, note, environment, releaseId, state, forecast, tags, linkedIssues, attachments, links, selectionMode."New value: +"Fields to update: name, note, environment, releaseId, state, forecast, tags, linkedIssues, attachments, links, selectionMode. status=\"closed\" closes the run."
  3. Addedv1.0.10

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description goes well past them: closing is permanent, freezes the run, snapshots remaining cases, snaps state to the project's "Done" option, and cannot be reopened via MCP. It also discloses the post-close read-only rule with its single exception (releaseId) and the write-permission requirement — precisely the irreversible consequences an agent needs before acting.

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 purpose and the permanence hazard, then fields, then format gotchas; the ordering matches decision priority. The allowed-fields sentence duplicates the schema's updates description and the closing semantics run long, but nearly every clause carries operational weight.

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?

For a destructive mutation with a nested free-form updates object, no output schema, and no enums, the description covers consequences, permission requirements, allowed values, inaccessibility of files, and the irreversibility window. An agent has everything needed to call it safely without guessing.

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; the description earns more by enumerating allowed update fields and by correcting a likely failure mode — updates.tags must be a JSON array of strings, not a comma-separated string, with a concrete example. It adds little about runId/projectId beyond the schema, which keeps it from a 5.

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?

Opens with a specific verb and resource: "Modify an existing manual test run, or close it." The dual mode (edit vs. close) is named up front, and the scope is narrow enough to separate it from update_run_test_case and update_manual_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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use rule for the dangerous path: send updates.status="closed" only when the user asks to close the run, never as part of another edit. It also states the partial-update convention (send only changed fields) and an explicit out-of-scope case (files cannot be added over MCP — use the TestDino UI).

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