Skip to main content
Glama

update_release

Modify an existing release by updating specific fields like name, description, dates, and status. Send only the fields you want to change.

Instructions

Modify an existing release. Send only the fields you want to change inside the updates object. Requires write permission. Fields: name, description, note, type, startDate, endDate, isStarted, isCompleted, startedAt, completedAt, linkedIssues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID (required).
releaseIdYesInternal _id or counter-style ID (required).
updatesYesFields to update: name, description, note, type, startDate, endDate, isStarted, isCompleted, startedAt, completedAt, linkedIssues.

Implementation Reference

  • Main handler function for the update_release tool. Validates inputs (projectId, releaseId, updates), constructs the PATCH request URL using endpoints, calls the API with apiRequestJson, and returns the response.
    export async function handleUpdateRelease(args?: UpdateReleaseArgs) {
      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?.releaseId) throw new Error("releaseId 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.updateRelease(
          String(args.projectId),
          String(args.releaseId)
        );
        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 release: ${msg}`);
      }
    }
  • Type definition (UpdateReleaseArgs) and tool registration object (updateReleaseTool) with input schema defining required fields: projectId, releaseId, and updates object.
    interface UpdateReleaseArgs {
      projectId: string;
      releaseId: string;
      updates: Record<string, unknown>;
    }
    
    export const updateReleaseTool = {
      name: "update_release",
      description:
        "Modify an existing release. Send only the fields you want to change inside the `updates` object. Requires write permission. Fields: name, description, note, type, startDate, endDate, isStarted, isCompleted, startedAt, completedAt, linkedIssues.",
      inputSchema: {
        type: "object",
        properties: {
          projectId: { type: "string", description: "Project ID (required)." },
          releaseId: {
            type: "string",
            description: "Internal _id or counter-style ID (required).",
          },
          updates: {
            type: "object",
            description:
              "Fields to update: name, description, note, type, startDate, endDate, isStarted, isCompleted, startedAt, completedAt, linkedIssues.",
          },
        },
        required: ["projectId", "releaseId", "updates"],
      },
    };
  • src/index.ts:289-293 (registration)
    Registration in the main server handler: routes the tool call name 'update_release' to the handleUpdateRelease function.
    if (name === "update_release") {
      return await handleUpdateRelease(
        args as Parameters<typeof handleUpdateRelease>[0]
      );
    }
  • src/index.ts:117-130 (registration)
    Tool is listed in the tools array (line 117) which is registered via ListToolsRequestSchema (line 135-137).
      updateReleaseTool,
      // Manual runs
      listManualRunsTool,
      getManualRunTool,
      createManualRunTool,
      updateManualRunTool,
      listRunTestCasesTool,
      updateRunTestCaseTool,
      // Sessions
      listSessionsTool,
      getSessionTool,
      createSessionTool,
      updateSessionTool,
    ];
  • Endpoint URL builder: constructs the PATCH URL for updating a release at /api/mcp/releases/:projectId/:releaseId.
    updateRelease: (projectId: string, releaseId: string): string => {
      const baseUrl = getBaseUrl();
      return `${baseUrl}/api/mcp/releases/${projectId}/${releaseId}`;
    },
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the need for write permission and implies a partial update pattern. It does not detail side effects or response behavior, but it adequately sets expectations for a mutation tool.

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?

The description is a single sentence followed by a field list. It wastes no words, front-loads the action, and lists all relevant fields. Every sentence 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?

Given no output schema, the description does not explain the return value. However, it covers all input parameters and usage hints. It is nearly complete for a simple update tool, missing only details about the response.

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?

The input schema has 100% coverage, describing each parameter. The description adds value by explaining the 'updates' object contains only fields to change, reinforcing the partial update semantics. This improves usability beyond the schema alone.

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 release.' The verb 'modify' and resource 'release' are specific. The list of updateable fields distinguishes it from sibling tools that operate on different resources (e.g., manual runs, sessions).

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 instructs to 'Send only the fields you want to change inside the `updates` object,' which guides partial updates. It also mentions 'Requires write permission.' However, it stops short of explicitly stating when not to use or alternatives like creating a new release.

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