Skip to main content
Glama
zereight

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_ci_catalog_resources

Read-only

List and filter GitLab CI/CD Catalog resources visible to you, with search, topics, and pagination. Use it to browse collections; for a single known resource, choose the get tool instead.

Instructions

List GitLab CI/CD Catalog resources/components visible to the user. Use this for a collection of resources; choose the corresponding get tool when you already know the single resource to inspect. It is read-only and does not mutate GitLab data; missing resources, invalid identifiers, insufficient permission, and rate limits are returned as errors. When project_id or group_id is accepted, provide the numeric ID or complete URL-encoded path described by the schema; use required identifiers and pagination fields exactly as documented.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order
afterNoGraphQL cursor for the next page
firstNoNumber of resources to return (default: 20, max: 100)
scopeNoCatalog resource scope
searchNoSearch catalog resources by name or description
topicsNoFilter by project topic names
jmespathNoOptional JMESPath expression filtering the JSON result before return.
group_idsNoFilter to catalog resources in these group IDs
verification_levelNoFilter by verification level

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.66
    • addedInput schema / properties / jmespath
      Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}
  2. Addedv2.1.45
  3. Removedv2.1.43
  4. Addedv2.1.26

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description reinforces the read-only nature and adds valuable behavioral context about error conditions: missing resources, invalid identifiers, insufficient permission, and rate limits are returned as errors. This goes beyond the annotations without contradicting them.

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?

Three sentences with no filler. The purpose is front-loaded, the alternative is named, and the error behavior is stated compactly. Every sentence earns its place.

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

Completeness4/5

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

The description covers purpose, usage boundaries, read-only behavior, and error handling, which is strong for a list tool. The slight mismatch in the identifier parameter name prevents a perfect score, and there is no return-shape description, though no output schema exists to clarify that.

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 coverage is 100%, so the baseline is 3. The description adds only generic advice about pagination and identifiers, and its mention of 'project_id' or 'group_id' does not match the actual schema parameters (e.g., group_ids, not group_id). Thus it adds little parameter-level meaning beyond the schema.

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?

The description states a specific verb and resource: 'List GitLab CI/CD Catalog resources/components visible to the user.' It also explicitly distinguishes itself from the single-resource get tool, so an agent can tell this list operation apart from get_ci_catalog_resource.

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

Usage Guidelines5/5

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

It gives clear when-to-use guidance: 'Use this for a collection of resources; choose the corresponding get tool when you already know the single resource to inspect.' It also mentions pagination and identifier handling, giving the agent actionable context for invocation.

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