Skip to main content
Glama
jmrplens

Gitlab MCP Server

by jmrplens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

GitLab Find Action

gitlab_find_action
Read-onlyIdempotent

Search the local GitLab action catalog to find action IDs and parameters when unclear. Returns schemas, hints, destructive flags, and examples without calling the GitLab API.

Instructions

Search the local GitLab action catalog. Read-only and no GitLab API call. Use when the action ID or params are unclear. Returns schemas, hints, destructive flags, and execute examples. Example: {"query":"issue list"}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matches to return. Defaults to 20 and is capped at 50.
queryYesSearch terms combining a GitLab domain or resource with a verb, filter, or object name, such as project create, merge request approve, pipeline retry, issue delete, or ci variable. At most 256 characters: a longer query is refused, not truncated.
explainNoWhen true, include deterministic scoring reasons for each returned action. Defaults to false to keep responses compact.

Output Schema

NameRequiredDescriptionDefault
countYesNumber of returned matches.
queryYesOriginal search query.
resultsYesMatching GitLab catalog actions with schemas and execute examples.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.3.0
    • addedOutput schema / properties / results / items / properties / required_params_any_of
      Added value: +{
+  "description": "Alternative groups: a call also needs every name of one group, not all groups.",
+  "items": {
+    "items": {
+      "type": "string"
+    },
+    "type": [
+      "null",
+      "array"
+    ]
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
  2. Changed2 schema fields changedv3.0.0
    • changedInput schema / properties / query / description
      Previous value: -"Search terms combining a GitLab domain or resource with a verb, filter, or object name, such as project create, merge request approve, pipeline retry, issue delete, or ci variable."New value: +"Search terms combining a GitLab domain or resource with a verb, filter, or object name, such as project create, merge request approve, pipeline retry, issue delete, or ci variable. At most 256 characters: a longer query is refused, not truncated."
    • addedInput schema / properties / query / maxLength
      Added value: +256
  3. Changed4 schema fields changedv2.1.3
    • changedOutput schema / properties / results / items / properties / example / description
      Previous value: -"Example gitlab_execute_tool call."New value: +"Example gitlab_execute_action call."
    • changedOutput schema / properties / results / items / properties / example / properties / arguments / description
      Previous value: -"Example arguments for gitlab_execute_tool."New value: +"Example arguments for gitlab_execute_action."
    • changedOutput schema / properties / results / items / properties / id / description
      Previous value: -"Canonical action ID to pass to gitlab_execute_tool."New value: +"Canonical action ID to pass to gitlab_execute_action."
    • changedOutput schema / properties / results / items / properties / required_params / description
      Previous value: -"Required parameter names captured from the input schema."New value: +"Required action-specific parameter names to place inside gitlab_execute_action params."
  4. Changed1 schema field changedv2.0.2
    • changedInput schema / properties / query / description
      Previous value: -"Search terms for GitLab actions, such as project create, merge request approve, pipeline retry, or ci variable."New value: +"Search terms combining a GitLab domain or resource with a verb, filter, or object name, such as project create, merge request approve, pipeline retry, issue delete, or ci variable."
  5. Addedv2.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely new context: the lookup is local with no GitLab API call, and it discloses the return contents (schemas, hints, destructive flags, execute examples), which helps an agent understand cost and payoff.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the verb and the local/no-API constraint, then the usage condition, then the return payload, ending with a minimal example. Every sentence carries distinct information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be enumerated, yet the description still summarizes them; parameters are fully covered by the schema and the usage trigger is stated. Nothing an agent needs to select or call this tool is missing.

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 query/limit/explain are fully documented in the schema itself. The example {"query":"issue list"} is a concrete illustration but adds little beyond the schema's own query-format guidance, so the baseline of 3 applies.

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?

States a specific verb and resource ("Search the local GitLab action catalog") plus scope qualifiers ("local", "no GitLab API call"). The clause "Use when the action ID or params are unclear" functionally separates it from the gitlab_execute_action sibling without needing the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when the action ID or params are unclear" gives a clear triggering condition and implies the converse path (use execute when they are clear). It stops short of naming the alternative tool or stating exclusions explicitly, so it is clear context rather than a full routing rule.

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