Skip to main content
Glama
Sign In
gitlab-api

gitlab-api

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gitlab Ingest Projects

gitlab_ingest_projects

Ingest GitLab projects into the medulla knowledge graph as typed Project nodes, including GitLabGroup and partOfGroup links, so project-group relationships become queryable.

Instructions

Natively ingest GitLab projects into medulla as typed :Project nodes.

Lists projects via the GitLab API and pushes them (with their :GitLabGroup + :partOfGroup links) into the knowledge graph via the fast engine client. Native-ingestion failures propagate to the caller. CONCEPT:AU-KG.ingest.enterprise-source-extractor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitlab_ingest_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownedNoOnly owned projects.
searchNoOnly projects matching this text.
per_pageNoProjects per page.
max_pagesNoMaximum pages to read.
membershipNoOnly projects the caller is a member of.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv27.3.20
    • addedInput schema / properties / max_pages
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Maximum pages to read."
+}
    • addedInput schema / properties / membership
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only projects the caller is a member of."
+}
    • addedInput schema / properties / owned
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only owned projects."
+}
    • removedInput schema / properties / params_json
      Removed value: -{
-  "default": "{}",
-  "description": "JSON string of get_projects filters (e.g. membership, per_page).",
-  "type": "string"
-}
    • addedInput schema / properties / per_page
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Projects per page."
+}
    • addedInput schema / properties / search
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only projects matching this text."
+}
  2. First observedv27.3.13

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description still discloses the important behavior: this is a write operation that creates :Project nodes with :GitLabGroup and :partOfGroup links via the fast engine client, and that ingestion failures propagate rather than being swallowed. It does not address idempotency/upsert semantics or authentication needs, which are meaningful gaps for an ingest tool.

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 core purpose is front-loaded in the first sentence and the three sentences are dense and relevant. The trailing 'CONCEPT:AU-KG.ingest.enterprise-source-extractor' tag adds internal taxonomy that does not help an agent decide or invoke.

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 mutation-style tool with five parameters, no annotations, and no output schema, the description covers destination and failure behavior but omits idempotency, whether it returns counts/status, and any scope limits on how much is ingested. Enough to call it, not enough to call it safely twice.

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 owned, search, per_page, max_pages, and membership are already documented in the schema. The description adds no guidance on how the pagination parameters interact (e.g. that max_pages caps the ingest) or what the defaults mean in practice.

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 and resource ('Natively ingest GitLab projects') plus the destination ('into medulla as typed :Project nodes'), which clearly separates it from sibling readers like gitlab_get_projects and from gitlab_ingest_pipelines by resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intent to populate a knowledge graph is implied by the wording, but there is no explicit statement of when to choose this over gitlab_get_projects or when ingestion should be avoided (e.g. re-runs). The agent must infer the triggering condition from the verb alone.

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