Skip to main content
Glama

get_release

Retrieve full release details: dates, status, linked issues, parent/root, and test progress stats. Requires project and release identifiers.

Instructions

Get the full details of one release: dates, status, linked issues, parent/root, and rolled-up progress stats (run counts, test status breakdown). releaseId accepts either the internal _id or a counter-style ID like 'MS-12'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID (required).
releaseIdYesInternal _id or counter-style ID (required).

Implementation Reference

  • Handler function for get_release tool. Validates inputs (projectId, releaseId), calls the API endpoint, and returns the release details as JSON.
    export async function handleGetRelease(args?: GetReleaseArgs) {
      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");
    
      try {
        const url = endpoints.getRelease({
          projectId: args.projectId,
          releaseId: args.releaseId,
        });
        const response = await apiRequestJson<unknown>(url, {
          headers: { Authorization: `Bearer ${token}` },
        });
        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 get release: ${msg}`);
      }
    }
  • Schema/definition for get_release tool, including name, description, and input schema requiring projectId and releaseId.
    export const getReleaseTool = {
      name: "get_release",
      description:
        "Get the full details of one release: dates, status, linked issues, parent/root, and rolled-up progress stats (run counts, test status breakdown). releaseId accepts either the internal _id or a counter-style ID like 'MS-12'.",
      inputSchema: {
        type: "object",
        properties: {
          projectId: { type: "string", description: "Project ID (required)." },
          releaseId: {
            type: "string",
            description: "Internal _id or counter-style ID (required).",
          },
        },
        required: ["projectId", "releaseId"],
      },
    };
  • src/index.ts:279-283 (registration)
    Registration routing: when tool name is 'get_release', dispatches to handleGetRelease.
    if (name === "get_release") {
      return await handleGetRelease(
        args as Parameters<typeof handleGetRelease>[0]
      );
    }
  • src/index.ts:48-49 (registration)
    Imports getReleaseTool and handleGetRelease into the main index.
    getReleaseTool,
    handleGetRelease,
  • Helper endpoint builder that constructs the URL for the get_release API call (GET /api/mcp/releases/:projectId/:releaseId).
    getRelease: (params: { projectId: string; releaseId: string }): string => {
      const baseUrl = getBaseUrl();
      const { projectId, releaseId } = params;
      return `${baseUrl}/api/mcp/releases/${projectId}/${releaseId}`;
    },
Behavior3/5

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

No annotations provided, so the description bears full responsibility. It discloses the output contents but does not address permissions, side effects, or idempotency. As a read operation, it is adequate but not rich in transparency.

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 two sentences: the first states the tool's purpose and output, the second explains the parameter. No redundant information, every sentence is essential.

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 lists the types of details returned (dates, status, etc.), providing a reasonable overview. However, it lacks specification of exact structure or permissions needed for a fully complete context.

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 provides 100% coverage with descriptions for both parameters. The description adds value by specifying that releaseId accepts counter-style IDs like 'MS-12', which goes beyond the schema.

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 'Get the full details of one release' and enumerates the specific details included (dates, status, linked issues, parent/root, progress stats). It also explains the releaseId parameter accepts two formats, distinguishing it from list_releases.

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 implies usage for retrieving full details of a single release, contrasting with list_releases. However, it does not explicitly state when to choose this over siblings or mention any preconditions or exclusions.

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