Skip to main content
Glama
orchestra-hq

Orchestra MCP Server

Official
by orchestra-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Pipeline Context

pipeline_context
Read-only

Fetch a pipeline's metadata, YAML definition, task integrations, last 7 days of run outcomes, and median success duration to inform edits or reasoning. Accepts an ID or alias.

Instructions

What an agent needs before editing or reasoning about a pipeline: its metadata, its full definition (the pipeline YAML structure as JSON), the integrations its tasks use, its recent run outcomes, and the median duration of its succeeded runs. Takes a pipeline ID or an alias. Run history covers the last 7 days, the widest window the API serves.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoAct on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers.
pipeline_id_or_aliasYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / account_id
      Added value: +{
+  "anyOf": [
+    {
+      "format": "uuid4",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Act on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers."
+}
  2. First observedv0.1.0

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, so the description adds meaningful behavioral detail: it discloses the return payload (metadata, YAML as JSON, integrations, run outcomes, median duration) and the data freshness limit (last 7 days, the widest window the API serves). It does not cover auth requirements beyond the schema's account_id note or failure behavior, but the added scope and window information is substantive.

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, front-loaded with the purpose and contents, then the parameter form, then the run-window constraint. Every sentence adds information without filler.

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

Completeness4/5

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

An output schema exists, so the description need not explain return structure, and it sufficiently covers what is returned, the accepted identifier form, and the run history window. Minor gaps remain around run-count limits or error behavior, but the definition is complete enough for correct invocation.

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 50%: account_id is fully documented in the schema, but the required pipeline_id_or_alias has no schema description. The description compensates by stating 'Takes a pipeline ID or an alias,' which adds the alias option beyond the bare string type.

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 the resource (a pipeline) and enumerates exactly what the tool returns: metadata, full definition as JSON, integrations, recent run outcomes, and median succeeded-run duration. This composite scope clearly distinguishes it from siblings like get_pipeline or get_pipeline_data, which cover only subsets.

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?

'What an agent needs before editing or reasoning about a pipeline' gives explicit usage context. However, it does not name alternatives or state when not to use this tool versus get_pipeline, get_pipeline_data, or list_pipeline_runs.

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