Skip to main content
Glama

gitlab_list_all_releases

Retrieve all release information for a specified GitLab project to track version history and deployment status.

Instructions

Fetches releases for a given GitLab project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesThe path of the GitLab project (e.g., "namespace/project-name").

Implementation Reference

  • Core handler function that fetches and returns all releases for the specified GitLab project using the GitLab API.
    // New tool: Get Releases for a Project
    async getReleases(projectPath: string): Promise<any[]> {
      const encodedProjectPath = encodeURIComponent(projectPath);
      return this.callGitLabApi<any[]>(`projects/${encodedProjectPath}/releases`);
    }
  • MCP server request handler that processes calls to the 'gitlab_list_all_releases' tool by invoking the GitLabService.getReleases method.
    case 'gitlab_list_all_releases': {
      if (!gitlabService) {
        throw new Error('GitLab service is not initialized.');
      }
      const { projectPath } = args as { projectPath: string };
      const result = await gitlabService.getReleases(projectPath);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:238-251 (registration)
    Tool registration in the allTools array, including name, description, and input schema for the MCP server.
      name: 'gitlab_list_all_releases',
      description: 'Fetches releases for a given GitLab project.',
      inputSchema: {
        type: 'object',
        properties: {
          projectPath: {
            type: 'string',
            description:
              'The path of the GitLab project (e.g., "namespace/project-name").',
          },
        },
        required: ['projectPath'],
      },
    },
  • Input schema definition validating the projectPath parameter for the tool.
      inputSchema: {
        type: 'object',
        properties: {
          projectPath: {
            type: 'string',
            description:
              'The path of the GitLab project (e.g., "namespace/project-name").',
          },
        },
        required: ['projectPath'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('fetches') but does not mention key traits like read-only nature, pagination, error handling, or authentication requirements, leaving significant gaps for a tool that likely interacts with an external API.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized, making it easy to understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is insufficient for a tool that likely returns a list of releases. It does not explain the return format, error conditions, or behavioral aspects, leaving the agent with incomplete information for proper invocation and handling.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema fully documents the single parameter 'projectPath'. The description adds no additional meaning beyond the schema, such as examples or constraints, but the baseline score of 3 is appropriate since the schema handles the parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('fetches') and resource ('releases for a given GitLab project'), making the purpose understandable. However, it does not differentiate from the sibling tool 'gitlab_list_releases_since_version', which suggests a more specific scope, leaving room for improvement in sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as the sibling 'gitlab_list_releases_since_version' for filtered releases. It lacks context on prerequisites or exclusions, offering only basic usage without comparative advice.

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/HainanZhao/mcp-gitlab-jira'

If you have feedback or need assistance with the MCP directory API, please join our Discord server