Skip to main content
Glama

close_issue

Update the status of a GitLab issue to closed using its project ID and issue IID.

Instructions

Close an issue.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
issue_iidYes
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'close_issue' tool handler function. It sends a PUT request to the GitLab API with state_event='close' to close an issue. Registered via @mcp.tool() decorator on line 957.
    @mcp.tool()
    async def close_issue(project_id: int, issue_iid: int, token: str = None, ctx=None) -> str:
        """Close an issue.
        
        Args:
            project_id: GitLab project ID
            issue_iid: Issue IID
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = {"state_event": "close"}
        result = await make_gitlab_request(f"/projects/{project_id}/issues/{issue_iid}", "PUT", data, ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error closing issue: {result['error']}"
        
        return f"Issue closed: #{result['iid']} - {result['title']}"
  • The 'close_issue' tool is registered as an MCP tool via the @mcp.tool() decorator on the async function at line 957.
    @mcp.tool()
    async def close_issue(project_id: int, issue_iid: int, token: str = None, ctx=None) -> str:
  • The make_gitlab_request helper function used by close_issue to make the API call to GitLab's REST 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 provided; description merely states 'Close an issue' without detailing side effects, permissions, or state requirements.

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

Conciseness3/5

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

Description is very short but includes a docstring-style argument list; it is concise but lacks richness.

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 missing annotations and simple tool, the description fails to mention success indicators, error conditions, or prerequisites, making it incomplete.

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 description coverage is 0%; the description restates parameter names with minimal clarification (e.g., 'GitLab project ID') but adds no meaningful semantics beyond the schema.

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?

The description 'Close an issue' clearly states the verb 'close' and the resource 'issue', and distinguishes from siblings like 'create_issue' or 'update_issue'.

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

Usage Guidelines3/5

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

The description implies usage when an issue needs to be closed, but provides no explicit guidance on when to use this vs. alternatives like 'update_issue'.

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