gitlab-api

Get group deploy tokens

gitlab_get_group_deploy_tokens

Read-onlyIdempotent

Retrieve deploy tokens for a specific GitLab group, with optional filters for name, username, scopes, and expiration. Use it to audit or manage group-level deploy credentials.

Instructions

Get deploy tokens for a specific group.

Args: **kwargs: Additional parameters for the request (e.g., group_id).

Returns: Response: A wrapper containing the original response and a list of DeployToken models.

Raises: ParameterError: If invalid parameters are provided. MissingParameterError: If required parameters are missing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitlab_get_group_deploy_tokens"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`page`	No
`token`	No
`scopes`	No
`group_id`	No
`per_page`	No
`username`	No
`max_pages`	No
`expires_at`	No
`project_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv27.3.20Nov 7, 2026

removedInput schema / properties / api_parameters

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

changedInput schema / properties / page / default
```
Previous value: -1New value: +null
```
changedInput schema / properties / per_page / default
```
Previous value: -100New value: +null
```

First observedv27.3.13Oct 25, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already declare this as read-only, idempotent, non-destructive, and open-world, so the safety profile is clear. The description adds useful return and error context, but omits pagination behavior despite page, per_page, and max_pages parameters.

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?

The purpose is front-loaded and the description is short, but the Args/Returns/Raises boilerplate adds little actionable detail. The kwargs line is not especially informative given the concrete parameters in the schema.

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 tool with 10 parameters, 0% schema description coverage, and no output schema, the description is incomplete. It gives the group scope and return type but leaves most parameter semantics and pagination/filtering behavior undocumented.

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% across 10 parameters, so the description must compensate. It only mentions group_id as an example under kwargs and does not explain name, token, scopes, username, expires_at, project_id, or pagination parameters.

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 states a specific verb and resource: get deploy tokens for a specific group. This distinguishes it from the project and singular token variants by scope, though it does not explicitly name those sibling alternatives.

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 phrase 'for a specific group' implies when to use this tool rather than the all-token or project-token variants. However, there are no explicit when-to-use or when-not-to-use guidelines, nor are alternatives named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server