mcp-gitlab-crunchtools

Overview Schema Source Related Servers Discussions Admin

List Group Projects Tool

list_group_projects_tool

Read-only

Retrieve projects within a GitLab group, with options to filter by name, visibility, and include subgroups. Supports sorting and pagination for efficient project discovery.

Instructions

List projects within a GitLab group.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group_id": "<group_id>"
    },
    "name": "list_group_projects_tool"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number (default: 1)
`sort`	No	Sort direction (asc, desc)	desc
`search`	No	Filter projects by name
`group_id`	Yes	Group ID or path
`order_by`	No	Order by field (created_at, updated_at, name, path)	created_at
`per_page`	No	Results per page, max 100 (default: 20)
`visibility`	No	Filter by visibility (public, internal, private)
`include_subgroups`	No	Include projects from subgroups

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Aug 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The readOnlyHint annotation already declares this is a safe read operation, so the description need only add extra context. It adds nothing — no mention of pagination behavior, whether subgroups are traversed by default, or what the returned project entries contain beyond what the output schema presumably covers.

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?

A single short sentence with no wasted words, front-loading the core purpose. It is efficient but sparse to the point of under-specification rather than over-verbosity.

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?

With eight parameters and a near-identical sibling (list_projects_tool), the description should clarify the group-scoping and subgroup behavior. The output schema and 100% param coverage handle the mechanics, but the sibling disambiguation gap leaves the definition incomplete for selection.

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 all eight parameters (including include_subgroups and visibility filters) are documented in the schema itself. The description contributes no additional parameter meaning, making the baseline 3 appropriate.

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 states a specific verb and resource ('List projects within a GitLab group'), so the action is unambiguous. However, it does not differentiate this tool from the sibling list_projects_tool or explain how group-scoped listing differs from general project listing.

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?

There is no guidance on when to use this tool versus list_projects_tool, nor any conditions or prerequisites. The agent must infer from the name alone that this is the group-scoped variant.

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

Deploy Server