Gitlab

Gitlab Get Project

gitlab_get_project

Read-onlyIdempotent

Get details for a specific GitLab project (e.g., project ID "123" or path "group/project"). Returns name, description, visibility, stars, forks, and default branch.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Project ID (numeric, e.g. "278964") or full path "namespace/project" (e.g. "gitlab-org/gitlab"). Pass the plain path — do NOT URL-encode it; the pack encodes it.
`_apiKey`	Yes	GitLab personal access token

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Project ID
`url`	Yes	Project web URL
`name`	Yes	Project name
`forks`	Yes	Fork count
`stars`	Yes	Star count
`topics`	Yes	Project topics/tags
`archived`	Yes	Whether project is archived
`full_path`	Yes	Full path with namespace
`namespace`	Yes	Namespace full path
`created_at`	Yes	Project creation timestamp
`visibility`	Yes	Project visibility (public/private/internal)
`description`	Yes	Project description
`open_issues`	Yes	Open issues count
`last_activity`	Yes	Last activity timestamp
`default_branch`	Yes	Default branch name

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 18, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-gitlab-api-key",
-    "id": "123"
-  },
-  {
-    "_apiKey": "your-gitlab-api-key",
-    "id": "group%2Fproject"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-gitlab-api-key",
+    "id": "123"
+  },
+  {
+    "_apiKey": "your-gitlab-api-key",
+    "id": "gitlab-org/gitlab"
+  }
+]

changedInput schema / properties / id / description

Previous value: -"Project ID (numeric) or URL-encoded path (e.g., \"group%2Fproject\")"New value: +"Project ID (numeric, e.g. \"278964\") or full path \"namespace/project\" (e.g. \"gitlab-org/gitlab\"). Pass the plain path — do NOT URL-encode it; the pack encodes it."

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "archived": {
+      "description": "Whether project is archived",
+      "type": "boolean"
+    },
+    "created_at": {
+      "description": "Project creation timestamp",
+      "type": "string"
+    },
+    "default_branch": {
+      "description": "Default branch name",
+      "type": "string"
+    },
+    "description": {
+      "description": "Project description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "forks": {
+      "description": "Fork count",
+      "type": "number"
+    },
+    "full_path": {
+      "description": "Full path with namespace",
+      "type": "string"
+    },
+    "id": {
+      "description": "Project ID",
+      "type": "number"
+    },
+    "last_activity": {
+      "description": "Last activity timestamp",
+      "type": "string"
+    },
+    "name": {
+      "description": "Project name",
+      "type": "string"
+    },
+    "namespace": {
+      "description": "Namespace full path",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "open_issues": {
+      "description": "Open issues count",
+      "type": "number"
+    },
+    "stars": {
+      "description": "Star count",
+      "type": "number"
+    },
+    "topics": {
+      "description": "Project topics/tags",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "url": {
+      "description": "Project web URL",
+      "type": "string"
+    },
+    "visibility": {
+      "description": "Project visibility (public/private/internal)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "full_path",
+    "description",
+    "url",
+    "stars",
+    "forks",
+    "open_issues",
+    "default_branch",
+    "visibility",
+    "archived",
+    "namespace",
+    "topics",
+    "created_at",
+    "last_activity"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-gitlab-api-key",
+    "id": "123"
+  },
+  {
+    "_apiKey": "your-gitlab-api-key",
+    "id": "group%2Fproject"
+  }
+]

First observedApr 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint. The description adds value by listing the specific returned fields (name, description, visibility, stars, forks, default branch), which is not present in annotations. No contradictions or missing behavioral context beyond what annotations provide.

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?

The description is a single, front-loaded sentence that immediately states the purpose and includes examples. Every word earns its place with no fluff or redundancy.

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

Completeness5/5

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

For a simple read-only tool with two parameters and an existing output schema, the description covers purpose, accepted input formats, and return values. There is no missing information an agent would need to call this tool correctly.

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 the schema fully documents both parameters, including the distinction between numeric ID and path and the instruction not to URL-encode. The description does not add additional parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 ('Get') and resource ('details for a specific GitLab project'), with explicit examples of acceptable IDs and a clear list of returned fields. It clearly differentiates from sibling tools like gitlab_list_projects (which lists multiple projects) and gitlab_get_file (which retrieves file content).

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?

The description implies use when a single project's details are needed by ID or path. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to infer the appropriate use case from the sibling set.

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

All Gitlab tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.