Skip to main content
Glama
chntif
by chntif

gitlab_list_labels

List labels of a GitLab project, with optional search, pagination, issue counts, and ancestor group labels.

Instructions

List labels of a GitLab project (/projects/:id/labels).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoGitLab project ID. Omit this field unless the user explicitly provided a value. When omitted, the tool tries the current runtime config defaults from WORKFLOW_ISSUE_PROJECT_ID or WORKFLOW_CODE_PROJECT_ID. If both are unset, or both are set to different values, the tool returns a missing-parameter error and you must pass project_id explicitly. Do not infer or auto-generate this value.
searchNoSearch text for label name/description.
pageNoPage number.
per_pageNoItems per page.
with_countsNoWhether to include issue counts.
include_ancestor_groupsNoWhether to include ancestor group labels.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded.
toolYesTool name.
dataNoLabel list payload for the target project.
error_typeNoError type when ok=false.
messageNoError message when ok=false.
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions the endpoint and does not describe pagination, rate limits, or whether the operation is read-only (though implied).

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, concise sentence that states the purpose without fluff. However, it could be slightly more informative without losing brevity.

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

Completeness3/5

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

Given the tool has 6 parameters and an output schema is present, the description could explain pagination behavior or search functionality. The existing description is adequate but not complete.

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 baseline is 3. The description adds no parameter-specific information beyond the schema's own descriptions.

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 clearly states the verb 'List' and the resource 'labels of a GitLab project', with the endpoint path. This distinguishes it from sibling tools like gitlab_create_label (create) and gitlab_delete_label (delete).

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?

No guidance on when to use this tool versus alternatives such as gitlab_create_label or gitlab_update_label. The description only states the action, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chntif/mcp-gitlab-workflow'

If you have feedback or need assistance with the MCP directory API, please join our Discord server