Skip to main content
Glama

unarchive_project

Restore an archived GitLab project to active state, enabling full access and modifications.

Instructions

Unarchive 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 'unarchive_project' tool handler function. It calls GitLab API POST /projects/{project_id}/unarchive to unarchive a previously archived project.
    @mcp.tool()
    async def unarchive_project(project_id: int, token: str = None, ctx=None) -> str:
        """Unarchive 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}/unarchive", "POST", ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error unarchiving project: {result['error']}"
        
        return f"Project {project_id} unarchived successfully"
  • The tool is registered via the @mcp.tool() decorator on line 722, which registers 'unarchive_project' as an MCP tool in the FastMCP server instance.
    @mcp.tool()
    async def unarchive_project(project_id: int, token: str = None, ctx=None) -> str:
        """Unarchive 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}/unarchive", "POST", ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error unarchiving project: {result['error']}"
        
        return f"Project {project_id} unarchived successfully"
Behavior1/5

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

No annotations provided. The description only repeats the tool name without disclosing effects, permissions, or side effects.

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?

Concise with a clear 'Args' section listing parameters; no unnecessary text.

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?

Very sparse description for a mutation tool; does not explain result, permissions, or relation to sibling tools.

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?

With 0% schema coverage, the description adds basic meanings for project_id and token, but lacks details on token scope or usage.

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 action ('Unarchive a project') with the specific resource, but does not differentiate from the sibling tool 'archive_project'.

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 (e.g., archive_project) or prerequisites (e.g., project must be archived).

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