Skip to main content
Glama

list_releases

Browse releases for a project. Filter by name, type, completion status, or parent release to find specific milestones.

Instructions

Browse releases (a.k.a. milestones) for a project. Use search to match by name; type filters by free-text release type; isCompleted filters by completion state; parentReleaseId returns the direct children of a release (releases nest up to 3 levels deep). Default page size 25 (max 200).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID (required).
searchNoMatch by release name.
typeNoRelease type. Either canonical ('iteration', 'major') or display ('Iteration', 'Major') form — server normalizes to lowercase so UI badge color matches.
isCompletedNo
parentReleaseIdNoDirect children of this release.
statusNoRelease status (project-specific).
sortByNo
sortOrderNo
pageNo
limitNoDefault 25 (max 200).

Implementation Reference

  • The main handler function that executes the list_releases tool logic. It calls the API endpoint and returns the response as tool content.
    export async function handleListReleases(args?: ListReleasesArgs) {
      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");
    
      try {
        const { parentReleaseId, ...rest } = args;
        const url = endpoints.listReleases({
          ...rest,
          ...(parentReleaseId ? { parentMilestone: parentReleaseId } : {}),
        });
        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 list releases: ${msg}`);
      }
    }
  • The ListReleasesArgs interface and inputSchema property of the tool definition, defining the input parameters (projectId required, optional search, type, isCompleted, parentReleaseId, status, sortBy, sortOrder, page, limit).
    interface ListReleasesArgs {
      projectId: string;
      search?: string;
      type?: string;
      isCompleted?: boolean;
      parentReleaseId?: string;
      status?: string;
      sortBy?: "createdAt" | "startDate" | "endDate" | "name";
      sortOrder?: "asc" | "desc";
      page?: number;
      limit?: number;
    }
    
    export const listReleasesTool = {
      name: "list_releases",
      description:
        "Browse releases (a.k.a. milestones) for a project. Use search to match by name; type filters by free-text release type; isCompleted filters by completion state; parentReleaseId returns the direct children of a release (releases nest up to 3 levels deep). Default page size 25 (max 200).",
      inputSchema: {
        type: "object",
        properties: {
          projectId: { type: "string", description: "Project ID (required)." },
          search: { type: "string", description: "Match by release name." },
          type: {
            type: "string",
            description:
              "Release type. Either canonical ('iteration', 'major') or display ('Iteration', 'Major') form — server normalizes to lowercase so UI badge color matches.",
          },
          isCompleted: { type: "boolean" },
          parentReleaseId: {
            type: "string",
            description: "Direct children of this release.",
          },
          status: {
            type: "string",
            description: "Release status (project-specific).",
          },
          sortBy: {
            type: "string",
            enum: ["createdAt", "startDate", "endDate", "name"],
          },
          sortOrder: { type: "string", enum: ["asc", "desc"] },
          page: { type: "number" },
          limit: { type: "number", description: "Default 25 (max 200)." },
        },
        required: ["projectId"],
      },
    };
  • src/index.ts:273-278 (registration)
    The routing logic in the tool call handler that dispatches 'list_releases' to handleListReleases.
    // Releases
    if (name === "list_releases") {
      return await handleListReleases(
        args as Parameters<typeof handleListReleases>[0]
      );
    }
  • src/index.ts:113-114 (registration)
    The tool is registered in the tools array passed to setRequestHandler(ListToolsRequestSchema), exposing it to MCP clients.
    // Releases
    listReleasesTool,
  • The endpoint URL builder that constructs the GET /api/mcp/releases/:projectId request with query parameters.
    listReleases: (params: {
      projectId: string;
      search?: string;
      type?: string;
      isCompleted?: boolean;
      parentMilestone?: string;
      status?: string;
      sortBy?: string;
      sortOrder?: string;
      page?: number;
      limit?: number;
    }): string => {
      const baseUrl = getBaseUrl();
      const { projectId, ...queryParams } = params;
      const queryString = buildQueryString(queryParams);
      return `${baseUrl}/api/mcp/releases/${projectId}${queryString}`;
    },
Behavior4/5

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

Discloses default page size, max limit, nesting depth (3 levels), and case normalization for type. Lacks explicit read-only assertion, but browsing intent is clear. No annotations to contradict.

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?

Two sentences, first covers purpose, second covers key filters and behaviors. No wasted words, information is front-loaded.

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?

Covers essential behaviors (pagination, nesting, filters) with 10 parameters and no output schema. Could mention sorting options, but schema enum suffices. Reasonably complete for a list tool.

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?

Description adds value beyond schema by explaining default page size for limit, nesting behavior for parentReleaseId, and case normalization for type. Schema coverage 60% is reasonable, and description compensates well.

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?

Clearly states 'Browse releases (a.k.a. milestones) for a project' with specific verb and resource. Distinguishes well from sibling tools like get_release (single) and create_release (creation).

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 on when to use each filter (search, type, isCompleted, parentReleaseId). Does not explicitly mention alternatives like get_release for a single release, but the context is clear enough.

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