Skip to main content
Glama
Sign In
gitlab-mcp

gitlab-mcp

by mcpland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Pipeline Test Report Summary

gitlab_get_pipeline_test_report_summary
Read-onlyIdempotent

Retrieve per-suite test counts and totals for a GitLab pipeline without listing individual test cases. Use the detailed test report tool when you need failure-level results.

Instructions

Get per-suite test counts and totals for a pipeline without individual test cases. Use gitlab_get_pipeline_test_report for failures.

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": {
      "pipeline_id": "<pipeline_id>"
    },
    "name": "gitlab_get_pipeline_test_report_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNo
pipeline_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive and open-world behavior, so the safety profile is fully covered. The description adds the useful note that output is aggregate per-suite data rather than case-level detail, but says nothing about pagination, response shape, or permission requirements for private projects.

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?

Two short sentences with zero filler; the primary function is stated first and the disambiguation second. Nothing could be removed without losing information.

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?

With no output schema, the description does adequately convey what comes back (per-suite counts and totals). However, for a two-parameter tool with zero schema coverage and no annotations gaps otherwise, the complete silence on project_id resolution leaves the definition only minimally sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description is expected to carry parameter meaning, and it does not. It never explains the required pipeline_id or the optional nullable project_id, leaving the agent to guess how project_id resolves when omitted.

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 names a specific verb and resource ('Get per-suite test counts and totals for a pipeline') and explicitly states the scope boundary ('without individual test cases'). This makes it immediately distinguishable from the sibling gitlab_get_pipeline_test_report, which returns the individual cases.

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 second sentence names an alternative tool and the condition that should route the agent there ('for failures'). What's missing is guidance on when this summary view is preferred over other pipeline inspection tools such as gitlab_get_pipeline, but the main fork is covered.

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