Skip to main content
Glama

transfer_project

Transfer a GitLab project to a different namespace, such as a user or group, by specifying the project ID and target namespace.

Instructions

Transfer a project to a new namespace.

Args:
    project_id: GitLab project ID
    namespace: Target namespace (user or group)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
namespaceYes
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'transfer_project' tool function that transfers a GitLab project to a new namespace via the GitLab API. It takes project_id, namespace, optional token and ctx, and makes a PUT request to /projects/{project_id}/transfer.
    async def transfer_project(project_id: int, namespace: str, token: str = None, ctx=None) -> str:
        """Transfer a project to a new namespace.
        
        Args:
            project_id: GitLab project ID
            namespace: Target namespace (user or group)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = {"namespace": namespace}
        result = await make_gitlab_request(f"/projects/{project_id}/transfer", "PUT", data, ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error transferring project: {result['error']}"
        
        return f"Project transferred: {result['name']} to {result['namespace']['full_path']}"
  • The '@mcp.tool()' decorator registers transfer_project as an MCP tool on the FastMCP server instance.
    @mcp.tool()
    async def transfer_project(project_id: int, namespace: str, token: str = None, ctx=None) -> str:
  • The function signature and docstring define the input schema: project_id (int), namespace (str), token (optional str), ctx (optional, auto-injected).
    async def transfer_project(project_id: int, namespace: str, token: str = None, ctx=None) -> str:
        """Transfer a project to a new namespace.
        
        Args:
            project_id: GitLab project ID
            namespace: Target namespace (user or group)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
Behavior2/5

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

No annotations are provided, so description must disclose behavior. It does not explain side effects (e.g., ownership changes, project location, or if original is deleted), only the action 'transfer'.

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 concise but structured as a plain list of arguments, lacking a clear summary or front-loaded purpose. It is functional but not well-organized.

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?

For a mutation tool with 4 params and an output schema, the description omits behavioral details (e.g., what happens to the project after transfer, permissions needed). Leaves significant gaps for safe usage.

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?

Schema has 0% description coverage, so description provides the only meaning. It lists parameters with minimal explanations (e.g., 'namespace: Target namespace (user or group)'). This is adequate but not rich.

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 clearly states 'Transfer a project to a new namespace', which is a specific verb and resource, distinguishing it from sibling tools like archive_project or delete_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., share_project_with_group) or when not to use it. No prerequisites or context for triggering the transfer.

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