Skip to main content
Glama
zereight

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_projects

Read-only

Retrieve GitLab projects accessible to the current user, with filters for ownership, membership, visibility, topic, search, and pagination. Read-only; errors return for missing resources, denied access, or rate limits.

Instructions

List projects accessible by the current user. For one known resource, use the matching get tool. Read-only; missing resources, denied access, and rate limits return errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)
sortNoReturn projects sorted in ascending or descending order
ownedNoFilter for projects owned by current user
topicNoFilter by topic (projects tagged with this topic)
searchNoSearch term for projects
simpleNoReturn only limited fields
archivedNoFilter for archived projects
jmespathNoOptional JMESPath expression filtering the JSON result before return.
order_byNoReturn projects ordered by field
per_pageNoNumber of items per page (max: 100, default: 20)
membershipNoFilter for projects where current user is a member
visibilityNoFilter by project visibility
min_access_levelNoFilter by minimum access level
search_namespacesNoNeeds to be true if search is full path
with_issues_enabledNoFilter projects with issues feature enabled
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.18
  3. Removedv2.1.14
  4. Addedv2.1.11
  5. Removedv2.1.10
  6. Changed2 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"
+}
  7. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new context by disclosing error behavior: missing resources, denied access, and rate limits all return errors. It does not describe pagination or return shape, keeping it short of a 5.

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 tight sentences with no waste; scope is front-loaded, then the alternative, then the error behavior. Every sentence earns its place.

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 16-parameter list tool with no output schema, the description covers scope, safety, and errors but says nothing about the shape of returned projects or pagination behavior. Params are fully covered by the schema, but the absent output schema leaves a real 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 description coverage is 100% across all 16 parameters, so the schema fully documents pagination, filters, sorting, and enums. The description adds no parameter guidance beyond what is already structured, so the baseline 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 ('List projects') plus the scope ('accessible by the current user'), and explicitly routes single-resource lookups to the sibling get tool. An agent can distinguish this from get_project without opening either 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?

Provides a clear usage rule: use this to list, use the matching get tool for one known resource. No explicit when-not beyond that (e.g., when to prefer my_issues or search_repositories), but the core routing decision is spelled out.

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