Skip to main content
Glama

share_project_with_group

Share a GitLab project with a group. Define access level (Guest to Owner) and optional expiration date.

Instructions

Share project with a group.

Args:
    project_id: GitLab project ID
    group_id: Group ID to share with
    group_access: Access level (10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner)
    expires_at: Expiration date (YYYY-MM-DD) (optional)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
group_idYes
group_accessYes
expires_atNo
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'share_project_with_group' tool. It shares a GitLab project with a group by making a POST request to /projects/{project_id}/share with group_id, group_access, and optional expires_at.
    @mcp.tool()
    async def share_project_with_group(project_id: int, group_id: int, group_access: int, expires_at: str = None, token: str = None, ctx=None) -> str:
        """Share project with a group.
        
        Args:
            project_id: GitLab project ID
            group_id: Group ID to share with
            group_access: Access level (10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner)
            expires_at: Expiration date (YYYY-MM-DD) (optional)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = {
            "group_id": group_id,
            "group_access": group_access
        }
        if expires_at:
            data["expires_at"] = expires_at
        
        result = await make_gitlab_request(f"/projects/{project_id}/share", "POST", data, ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error sharing project: {result['error']}"
        
        return f"Project shared with group {group_id} (access level: {group_access})"
  • Registration of the tool via the @mcp.tool() decorator on the async function.
    @mcp.tool()
  • Helper function used by share_project_with_group to make the actual GitLab API request with authentication 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)}
Behavior1/5

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

No annotations provided. Description fails to disclose side effects, permission requirements, or what happens on success/failure. As a mutation tool, this is a critical 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?

Description is concise, using a structured docstring format. No redundant sentences, but could be slightly more informative without losing conciseness.

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?

Despite an output schema existing, the description does not mention return values, errors, or post-conditions. Lacks complete context for a tool that modifies state.

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 no parameter descriptions (0% coverage). Description adds some meaning by listing allowed values for 'group_access' and format for 'expires_at', but overall adds limited value beyond schema field names.

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 clearly identifies the action ('Share project with a group') and the resource (project to group). It differentiates from sibling tool 'unshare_project_with_group'.

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. Does not specify prerequisites or conditions under which sharing is appropriate.

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