Skip to main content
Glama

gitlab_list_releases_since_version

Filter GitLab project releases from a specific version onward to track changes and updates in your development workflow.

Instructions

Filters releases for a given GitLab project since a specific version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNameYesThe name or partial name of the GitLab project.
sinceVersionYesThe version to filter releases since (e.g., "1.0.0").

Implementation Reference

  • Main handler for gitlab_list_releases_since_version tool. Resolves projectPath by fuzzy matching projectName, then calls service to filter releases since given version using semver comparison.
    case 'gitlab_list_releases_since_version': {
      if (!gitlabService) {
        throw new Error('GitLab service is not initialized.');
      }
      const { projectName, sinceVersion } = args as {
        projectName: string;
        sinceVersion: string;
      };
      const projects =
        await gitlabService.filterProjectsByName(projectName);
      if (projects.length === 0) {
        throw new Error(`No project found with name: ${projectName}`);
      }
      const projectPath = projects[0].path_with_namespace;
      const result = await gitlabService.filterReleasesSinceVersion(
        projectPath,
        sinceVersion,
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:253-270 (registration)
    Tool registration in the allTools array, defining name, description, and inputSchema for gitlab_list_releases_since_version.
      name: 'gitlab_list_releases_since_version',
      description:
        'Filters releases for a given GitLab project since a specific version.',
      inputSchema: {
        type: 'object',
        properties: {
          projectName: {
            type: 'string',
            description: 'The name or partial name of the GitLab project.',
          },
          sinceVersion: {
            type: 'string',
            description: 'The version to filter releases since (e.g., "1.0.0").',
          },
        },
        required: ['projectName', 'sinceVersion'],
      },
    },
  • Helper method in GitLabService that fetches all releases and filters those with tag_name >= sinceVersion using semver.gte.
    async filterReleasesSinceVersion(
      projectPath: string,
      sinceVersion: string,
    ): Promise<any[]> {
      const allReleases = await this.getReleases(projectPath);
      const semver = await import('semver');
    
      return allReleases.filter((release) => {
        try {
          return semver.gte(release.tag_name, sinceVersion);
        } catch (error) {
          console.error(
            `Could not parse version ${release.tag_name} or ${sinceVersion}: ${error}`,
          );
          return false;
        }
      });
    }
  • Helper method in GitLabService to fuzzy match projects by name and return matching GitLabProject objects; used to resolve projectPath from projectName in the handler.
    async filterProjectsByName(projectName: string): Promise<GitLabProject[]> {
      const allProjects = await this.listProjects();
      const lowerCaseProjectName = projectName.toLowerCase();
    
      return allProjects.filter(
        (project) =>
          project.name.toLowerCase().includes(lowerCaseProjectName) ||
          project.name_with_namespace
            .toLowerCase()
            .includes(lowerCaseProjectName),
      );
    }
  • Helper method in GitLabService to fetch all releases from GitLab API for a project; called by filterReleasesSinceVersion.
    async getReleases(projectPath: string): Promise<any[]> {
      const encodedProjectPath = encodeURIComponent(projectPath);
      return this.callGitLabApi<any[]>(`projects/${encodedProjectPath}/releases`);
    }
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 mentions filtering but doesn't describe key traits such as authentication requirements, rate limits, pagination behavior, error handling, or what the output looks like (e.g., list format, fields included). This is a significant gap for a tool that 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 function without unnecessary words. It's front-loaded with the core action and parameters, making it easy to parse 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 complexity of interacting with GitLab's API, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral aspects (e.g., auth, errors), output format, and usage context, leaving the agent poorly equipped to use the tool effectively in real scenarios.

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 already documents both parameters thoroughly. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't clarify version format constraints or project matching behavior), resulting in a baseline score of 3.

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 tool's purpose with a specific verb ('filters') and resource ('releases for a given GitLab project'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'gitlab_list_all_releases', which might cause confusion about when to use each.

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 like 'gitlab_list_all_releases' or other filtering methods. It mentions the filtering capability but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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