Skip to main content
Glama

get_repository_tags

Retrieve all tags from a GitLab repository by providing the project ID.

Instructions

Get repository tags.

Args:
    project_id: GitLab project ID
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the 'get_repository_tags' tool. It calls the GitLab API endpoint /projects/{project_id}/repository/tags to fetch tags and returns them formatted with name, commit short_id, and message.
    @mcp.tool()
    async def get_repository_tags(project_id: int, token: str = None, ctx=None) -> str:
        """Get repository tags.
        
        Args:
            project_id: GitLab project ID
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = await make_gitlab_request(f"/projects/{project_id}/repository/tags", ctx=ctx, token=token)
        
        if isinstance(data, dict) and "error" in data:
            return f"Error: {data['error']}"
        if not data:
            return "No tags found."
        
        tags = []
        for tag in data[:10]:
            tags.append(f"• {tag['name']} - {tag['commit']['short_id']} ({tag.get('message', 'No message')})")
        return "\n".join(tags)
  • The tool is registered as an MCP tool via the @mcp.tool() decorator on line 822.
    @mcp.tool()
    async def get_repository_tags(project_id: int, token: str = None, ctx=None) -> str:
Behavior2/5

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

No annotations and description does not disclose behavioral traits (e.g., permissions, rate limits, or default behavior for optional token).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise with clear parameter list. Could be more structured but no wasted sentences.

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

Completeness3/5

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

Output schema exists so return values not needed, but description lacks behavioral context for a simple read tool. Adequate but not thorough.

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

Parameters2/5

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

Schema coverage is 0%; description adds minimal meaning beyond parameter names (e.g., token optional, ctx injected). Lacks details on valid values or constraints.

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?

Describes retrieving repository tags with specific verb and resource. Clear but lacks detail on what tags are; distinct from siblings.

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?

No guidance on when or why to use this tool versus alternatives like get_project_branches or create_tag. No context provided.

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/skmprb/gitlab-clone-mcp-server'

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