Skip to main content
Glama

Get pipeline report

get_pipeline_report
Read-only

Read one report about a connected repository's Ankra pipeline. report picks it: test_history (one test's outcomes and flaky rate over recent runs of a branch; needs test_key), test_timings (mean duration per file or per test of one stage; needs stage), test_quarantine (the quarantine settings, the quarantined tests and the recently released ones), test_quarantine_candidates (flaky tests of the default branch that reach the thresholds and are not quarantined), caches (the repository's pipeline caches with size, last use and expiry), branches (each ref with its latest run and run counts), run_artifacts (the artifacts a run stored; needs pipeline_run_id) and run_findings (the code and container findings at a run's commit; needs pipeline_run_id). Address the repository with exactly one of repository_id, application_id, or owner and repo. Read-only; needs pipelines.read.

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": {
      "report": "<report>"
    },
    "name": "get_pipeline_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository name, with owner.
runsNotest_history and test_timings only: how many recent runs to read, 1 to 100 (default 30).
limitNoHow many rows of a listing report to return, 1 to 100; has_more says when there are more.
ownerNoRepository owner (organisation or user), with repo, instead of repository_id.
stageNoThe pipeline stage, for test_timings.
branchNotest_history and test_timings only: the branch to read; omitted reads the repository's default branch.
reportYesWhich report to read.
group_byNotest_timings only: mean per file (the default) or per test.
providerNoNarrows owner and repo when the same repository is connected on two providers.
test_keyNoThe test's key, for test_history (the quarantine reports carry it).
repository_idNoThe connected repository's id, from list_pipeline_repositories.
application_idNoAn application whose linked repository to address, instead of repository_id.
pipeline_run_idNoThe run, for run_artifacts and run_findings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds the required permission scope ("needs pipelines.read"), which is genuinely useful pre-call context the agent would otherwise not have. It also discloses that listing reports are paginated via limit/has_more, though the mechanics live in the schema.

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?

Front-loads the core action in the first sentence, then spends the second on the report catalog and the third on addressing rules. The report enumeration is dense but every clause carries a distinct report type, so little can be cut without losing routing information.

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 complex 13-parameter, 8-variant tool with no output schema, the description covers variant selection, per-variant prerequisites, addressing alternatives, and auth scope. Return-shape detail is the only gap, and report names plus schema descriptions largely cover expectations.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds cross-parameter dependencies the schema descriptions do not encode: which prerequisite parameter each report requires and the mutually exclusive repository addressing options. That conditional logic is the main source of invocation errors for a 13-parameter tool.

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?

Opens with a specific verb and resource ("Read one report about a connected repository's Ankra pipeline") and then enumerates every valid report kind with the data each returns, so an agent can distinguish test_history from caches from run_findings without opening the schema. The scope of 'one report' is unambiguous.

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?

Gives explicit conditional routing per report (test_history needs test_key, test_timings needs stage, run_artifacts/run_findings need pipeline_run_id) and states the addressing rule: exactly one of repository_id, application_id, or owner plus repo. It stops short of naming sibling alternatives such as get_pipeline_repository or get_pipeline_step_logs, so the when-not-to-use case is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.