Skip to main content
Glama
zereight

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_group_projects

Read-only

List GitLab projects in a group by group ID or path, with filters for search, visibility, topics, archived status, and subgroups. Returns paginated project details for read-only discovery and analysis.

Instructions

List projects in a group. 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
pageNoPage number for pagination (default: 1)
sortNoSort direction
topicNoFilter by topic (projects tagged with this topic)
searchNoSearch term to filter projects
starredNoFilter by starred projects
archivedNoFilter for archived projects
group_idYesGroup ID or path
jmespathNoOptional JMESPath expression filtering the JSON result before return.
order_byNoField to sort by
per_pageNoNumber of items per page (max: 100, default: 20)
statisticsNoInclude project statistics
visibilityNoFilter by project visibility
min_access_levelNoFilter by minimum access level
include_subgroupsNoInclude projects from subgroups
with_issues_enabledNoFilter projects with issues feature enabled
with_security_reportsNoInclude security reports
with_custom_attributesNoInclude custom attributes
with_programming_languageNoFilter by programming language
with_merge_requests_enabledNoFilter projects with merge requests feature enabled

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.18
  5. Removedv2.1.14
  6. Addedv2.1.11
  7. Removedv2.1.10
  8. Changed3 schema fields changedv2.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / topic
      Added value: +{
+  "description": "Filter by topic (projects tagged with this topic)",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "group_id"
+]
  9. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already carry readOnlyHint and openWorldHint, so the bar is lower; the description adds value beyond them by disclosing error behavior (missing resources, invalid identifiers, insufficient permission, rate limits returned as errors). No contradiction with annotations — the read-only claim aligns with readOnlyHint=true.

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 core purpose is front-loaded in the first sentence, and the description is compact at three sentences. However, phrases like 'read-only and does not mutate GitLab data' are redundant, and the final sentence is generic boilerplate that could apply to nearly any tool, diluting the value of the prose.

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?

For a 19-parameter tool with no output schema, the description covers purpose, routing, safety, and error behavior, leaving parameter details to the fully documented schema. It is adequate but incomplete: it does not describe the return format or pagination response shape, which matters since no output schema exists to fill that gap.

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 minor guidance about supplying numeric IDs or URL-encoded paths, but this largely restates the schema's 'Group ID or path' note and is somewhat generic boilerplate. It also references project_id, which is not a parameter in this schema, introducing slight inaccuracy.

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?

The description opens with a specific verb+resource ('List projects in a group') and explicitly contrasts itself with the 'corresponding get tool' for single-resource inspection, which differentiates it from siblings like get_project. However, it does not distinguish itself from the close sibling list_projects, leaving a plausible alternative ambiguous.

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?

Gives a clear decision rule: use for a collection of resources, and switch to the get tool when a single resource is known. This is explicit routing guidance, but it omits exclusions relative to list_projects and other list tools, so it falls short of fully covering when-not-to-use scenarios.

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