gitlab-api

Get runners

gitlab_get_runners

Read-onlyIdempotent

Retrieve GitLab runner details and filter them by scope, status, project, group, or tags to inspect CI/CD runner configuration and availability.

Instructions

Get information about runners.

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

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

Raises: ParameterError: If invalid parameters are provided.

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_runners"
  }
}

Input Schema

Name	Required	Description	Default
`data`	No
`info`	No
`token`	No
`active`	No
`locked`	No
`paused`	No
`status`	No
`group_id`	No
`tag_list`	No
`max_pages`	No
`runner_id`	No
`project_id`	No
`all_runners`	No
`description`	No
`runner_type`	No
`access_level`	No
`run_untagged`	No
`maximum_timeout`	No
`maintenance_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv27.3.20Nov 7, 2026

changedInput schema / properties / all_runners / default
```
Previous value: -falseNew value: +null
```

removedInput schema / properties / api_parameters

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

addedInput schema / properties / max_pages

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedv27.3.13Oct 25, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds that the response wraps the original response plus Runner models and that invalid parameters raise ParameterError, but it does not explain auth needs, pagination via max_pages, or how multiple filters interact.

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 description is short and front-loads the purpose, with efficient Returns and Raises sections. However, the Args/**kwargs boilerplate does not match the actual named schema parameters, and the example 'scope' is not a schema property, which can mislead.

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 19-parameter read tool with no output schema, the description is not complete enough to guide correct invocation. It omits filter semantics, the all_runners/group/project/runner_id distinction, and pagination behavior, though it does mention return wrapping and parameter errors.

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 19 parameters, and the description only offers generic kwargs with scope/status examples. It does not explain key parameters such as group_id, project_id, runner_id, all_runners, tag_list, or the distinction between list and single-runner retrieval.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the tool retrieves runner information, which identifies the resource and verb. However, it does not specify whether it lists all runners or filters by group/project/runner, and does not distinguish it from siblings such as gitlab_get_group_runners, gitlab_get_project_runners, or gitlab_get_runner.

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?

Provides no when-to-use guidance, prerequisites, or alternatives. An agent cannot infer from the description when this tool should be preferred over the more specific runner-retrieval siblings.

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

Deploy Server