Skip to main content
Glama

get_project_issues

Retrieve issues from a GitLab project. Filter by state (opened, closed, all) to view relevant tasks.

Instructions

Get issues for a GitLab project.

Args:
    project_id: GitLab project ID
    state: Issue state (opened, closed, all)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
stateNoopened
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_project_issues function implements the tool logic: it calls the GitLab API endpoint /projects/{project_id}/issues with a state filter, iterates over results (limited to 10), and returns formatted issue entries.
    @mcp.tool()
    async def get_project_issues(project_id: int, state: str = "opened", token: str = None, ctx=None) -> str:
        """Get issues for a GitLab project.
        
        Args:
            project_id: GitLab project ID
            state: Issue state (opened, closed, all)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        endpoint = f"/projects/{project_id}/issues?state={state}"
        data = await make_gitlab_request(endpoint, ctx=ctx, token=token)
        
        if isinstance(data, dict) and "error" in data:
            return f"Error: {data['error']}"
        
        if not data:
            return f"No {state} issues found."
        
        issues = []
        for issue in data[:10]:  # Limit to 10 issues
            issues.append(f"#{issue['iid']}: {issue['title']} - {issue['state']} ({issue['author']['name']})")
        
        return "\n".join(issues)
  • The @mcp.tool() decorator registers get_project_issues as an MCP tool on the FastMCP server instance.
    @mcp.tool()
  • The make_gitlab_request helper function is the underlying API request utility used by get_project_issues to communicate with the GitLab API.
    async def make_gitlab_request(endpoint: str, method: str = "GET", data: dict = None, ctx=None, token: str = None) -> dict[str, Any] | None:
        """Make a request to GitLab API with proper error handling."""
        # Priority: 1. Explicit token parameter, 2. Context headers, 3. Environment variable
        
        # If no explicit token provided, try to get from context
        if not token and ctx and hasattr(ctx, 'request_context') and ctx.request_context:
            # Try to get from request headers
            if hasattr(ctx.request_context, 'headers'):
                token = ctx.request_context.headers.get('GITLAB_TOKEN')
        
        # Fallback to environment variable
        if not token:
            token = os.getenv("GITLAB_TOKEN")
        
        if not token:
            return {"error": "GitLab token not provided. Please provide a token parameter, GITLAB_TOKEN in the request headers, or set the environment variable."}
        
        # Get GitLab URL (from context or environment)
        gitlab_url = os.getenv("GITLAB_URL", "https://gitlab.com")
        
        headers = {
            "PRIVATE-TOKEN": token,
            "Content-Type": "application/json"
        }
        
        url = f"{gitlab_url}/api/v4{endpoint}"
        
        async with httpx.AsyncClient() as client:
            try:
                if method == "GET":
                    response = await client.get(url, headers=headers, timeout=30.0)
                elif method == "POST":
                    response = await client.post(url, headers=headers, json=data, timeout=30.0)
                elif method == "PUT":
                    response = await client.put(url, headers=headers, json=data, timeout=30.0)
                elif method == "DELETE":
                    response = await client.delete(url, headers=headers, timeout=30.0)
                
                response.raise_for_status()
                return response.json() if response.content else {"success": True}
            except Exception as e:
                return {"error": str(e)}
Behavior2/5

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

No annotations are present, so the description must carry the burden. It does not explicitly state that the tool is read-only, safe, or idempotent. While 'get' implies reading, the absence of any behavioral disclosure (e.g., no side effects, authentication needs) is a gap.

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?

The description is brief with a clear first sentence and a structured list of parameters. No extraneous information. However, the list format is slightly verbose for a tool with only four parameters.

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?

An output schema exists, so return value details are not required. However, the description lacks information about pagination, error handling, or what happens when the project_id is invalid. For a list endpoint, these are relevant omissions.

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 has 0% coverage (no property descriptions), but the description compensates by listing each parameter with a brief explanation. Particularly helpful is the enumeration of allowed values for 'state' (opened, closed, all). This adds significant meaning beyond the schema.

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 verb 'Get' and the resource 'issues for a GitLab project', making the tool's purpose unambiguous. However, it does not differentiate this from sibling tools like close_issue or update_issue, which could cause confusion.

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 is provided on when to use this tool versus alternatives. For example, there is no mention that this tool is for listing issues, not for modifying or closing them. Usage context is entirely inferred from the name.

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