Skip to main content
Glama

update_manual_run

Modify an existing manual test run by sending updated fields. Supports name, note, tags, and more while keeping closed runs read-only except for release assignment.

Instructions

Modify an existing manual test run. Send only the fields you want to change inside the updates object. Requires write permission. Allowed fields: name, note, environment, releaseId, state, forecast, tags, linkedIssues, attachments, links, selectionMode. Closed runs are read-only except for releaseId (so a run can be re-attached to a different release). IMPORTANT: updates.tags must be a JSON array of strings — e.g. ["smoke","regression"] — NOT a comma-separated string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID (required).
runIdYesInternal _id or counter-style ID (required).
updatesYesFields to update: name, note, environment, releaseId, state, forecast, tags, linkedIssues, attachments, links, selectionMode.

Implementation Reference

  • The handler function for the update_manual_run tool. It validates arguments (projectId, runId, updates), builds the endpoint URL, sends a PATCH request with the updates, and returns the response.
    export async function handleUpdateManualRun(args?: UpdateManualRunArgs) {
      const token = getApiKey(args);
      if (!token) {
        throw new Error(
          "Missing TESTDINO_PAT environment variable. Configure it in your .cursor/mcp.json under 'env'."
        );
      }
      if (!args?.projectId) throw new Error("projectId is required");
      if (!args?.runId) throw new Error("runId is required");
      if (!args?.updates || typeof args.updates !== "object") {
        throw new Error("updates must be an object containing fields to modify");
      }
    
      try {
        const url = endpoints.updateManualRun(
          String(args.projectId),
          String(args.runId)
        );
        const response = await apiRequestJson<unknown>(url, {
          method: "PATCH",
          headers: { Authorization: `Bearer ${token}` },
          body: { updates: args.updates },
        });
        return {
          content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
        };
      } catch (error) {
        const msg = error instanceof Error ? error.message : String(error);
        throw new Error(`Failed to update manual run: ${msg}`);
      }
    }
  • The tool definition (updateManualRunTool) with name 'update_manual_run', description, and inputSchema (projectId, runId, updates). Also includes the UpdateManualRunArgs interface (lines 9-13).
    export const updateManualRunTool = {
      name: "update_manual_run",
      description:
        'Modify an existing manual test run. Send only the fields you want to change inside the `updates` object. Requires write permission. Allowed fields: name, note, environment, releaseId, state, forecast, tags, linkedIssues, attachments, links, selectionMode. Closed runs are read-only except for releaseId (so a run can be re-attached to a different release). IMPORTANT: updates.tags must be a JSON array of strings — e.g. ["smoke","regression"] — NOT a comma-separated string.',
      inputSchema: {
        type: "object",
        properties: {
          projectId: { type: "string", description: "Project ID (required)." },
          runId: {
            type: "string",
            description: "Internal _id or counter-style ID (required).",
          },
          updates: {
            type: "object",
            description:
              "Fields to update: name, note, environment, releaseId, state, forecast, tags, linkedIssues, attachments, links, selectionMode.",
          },
        },
        required: ["projectId", "runId", "updates"],
      },
    };
  • src/index.ts:61-62 (registration)
    Import of updateManualRunTool and handleUpdateManualRun from tools index.
    updateManualRunTool,
    handleUpdateManualRun,
  • src/index.ts:122-122 (registration)
    Tool registration in the tools array passed to server.setToolHandler.
    updateManualRunTool,
  • src/index.ts:311-315 (registration)
    Routing logic: when tool name is 'update_manual_run', it calls handleUpdateManualRun with the provided args.
    if (name === "update_manual_run") {
      return await handleUpdateManualRun(
        args as Parameters<typeof handleUpdateManualRun>[0]
      );
    }
Behavior4/5

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

Discloses mutation behavior, write permission requirements, and the constraint that closed runs are mostly read-only. Warns about tags format (must be JSON array). No annotations provided, so description carries full burden; it does well but could mention idempotency or error handling.

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?

Concise paragraph with front-loaded purpose. Every sentence adds value without redundancy. Efficiently conveys purpose, constraints, and critical format note.

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?

Comprehensive for a mutation tool with 3 required params and no output schema. Covers allowed fields, special behavior for closed runs, and tags format. Lacks mention of return value or side effects, but sufficient for typical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description adds significant value: lists allowed fields inside updates object, specifies tags format, and clarifies that runId can be internal _id or counter-style ID. This goes beyond the schema's 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?

The description clearly states 'Modify an existing manual test run' with a specific verb and resource. It lists allowed fields and distinguishes from sibling tools like create_manual_run 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 Guidelines4/5

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

Provides explicit guidance: send only changed fields in updates object, requires write permission, and notes that closed runs are read-only except for releaseId. However, it does not name an alternative tool for modifying closed runs beyond releaseId.

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