Skip to main content
Glama

unstar_project

Removes a star from a specified GitLab project by providing its project ID. Useful for managing project visibility and bookmarks.

Instructions

Unstar a project.

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 'unstar_project' tool handler function. It makes a POST request to the GitLab API endpoint /projects/{project_id}/unstar to unstar a project. The function takes a project_id parameter, an optional token, and an optional context. It returns a success message with the project name and updated star count, or an error message on failure.
    @mcp.tool()
    async def unstar_project(project_id: int, token: str = None, ctx=None) -> str:
        """Unstar a project.
        
        Args:
            project_id: GitLab project ID
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        result = await make_gitlab_request(f"/projects/{project_id}/unstar", "POST", ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error unstarring project: {result['error']}"
        
        return f"Project unstarred: {result['name']} (Stars: {result['star_count']})"
  • The tool is registered via the @mcp.tool() decorator on line 1140, which registers unstar_project as a FastMCP tool with the name matching the function name.
    async def unstar_project(project_id: int, token: str = None, ctx=None) -> str:
  • The function signature and docstring define the schema: project_id (int, required), token (str, optional), ctx (automatically injected). The return type is str. Type hints are provided in the function signature.
    async def unstar_project(project_id: int, token: str = None, ctx=None) -> str:
        """Unstar a project.
        
        Args:
            project_id: GitLab project ID
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
  • The make_gitlab_request helper function is used by unstar_project to make the actual HTTP POST request to the GitLab API. It handles token resolution (from parameter, request context, or environment variable), constructs the URL, and sends the request with error handling.
    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)}
Behavior3/5

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

With no annotations, the description carries the burden. It discloses the basic action but omits side effects, authorization requirements (token is optional but may be needed), or state changes. The simplicity of the tool mitigates this, but more detail would be helpful.

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?

Extremely concise: a one-line description followed by clear argument documentation. No unnecessary words, front-loaded with purpose, every sentence adds value.

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

Completeness4/5

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

For a simple unstar action, the description is complete enough. The output schema exists but is not detailed here, which is acceptable. It covers the key input parameters and basic action, though it lacks any mention of prerequisites or return value.

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?

Schema coverage is 0%, so description provides the only semantics. It explains project_id as 'GitLab project ID', token as 'GitLab Personal Access Token (optional)', and notes ctx is 'automatically injected'. This adds meaningful context beyond the raw 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?

Description states 'Unstar a project' which is a clear verb+resource pair. It directly contrasts with the sibling 'star_project', making the purpose unambiguous.

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 to use this tool versus alternatives like 'star_project' or other project actions. The description only states the action, leaving the agent to infer usage from context.

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