Skip to main content
Glama
Knuckles-Team

gitlab-api

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Api Request

api_request

Execute custom GitLab REST API calls by providing an HTTP method, endpoint, and optional JSON parameters. Use it to retrieve or modify GitLab resources not covered by other tools.

Instructions

Execute arbitrary GitLab REST API requests directly.

Input Schema

NameRequiredDescriptionDefault
methodYesHTTP method to use (e.g. GET, POST, PUT, DELETE, PATCH)
endpointYesThe API endpoint path (e.g., /projects/1/issues)
params_jsonNoJSON string of query parameters or body payload to pass to the request.{}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv27.3.13

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Arbitrary' hints that any method can be used, but it does not disclose authentication requirements, destructive potential, rate limits, or how raw responses are returned.

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?

The description is a single front-loaded sentence with no wasted words. It is arguably under-specified, but structurally it is efficient and clear.

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 generic passthrough tool with no annotations and no output schema, the description should explain when this is appropriate, safety considerations, and response handling. It omits all of these.

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 description coverage is 100%, so method, endpoint, and params_json are already fully documented in the schema. The description adds no parameter meaning beyond that, which is the baseline expectation when the schema is complete.

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?

It states a clear verb and resource: execute GitLab REST API requests. It implicitly distinguishes itself from the GraphQL sibling by naming REST, but does not differentiate from the many specific REST operation tools.

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?

The description gives no guidance on when to use this generic escape hatch versus the dedicated siblings such as gitlab_create_issue or gitlab_get_project. It also gives no warning about when not to use it.

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

Deploy Server

Other Tools