Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Create a pipeline

create_pipeline

Create a new pipeline from a JSON definition and optionally validate its schema before saving, so you can add pipelines to Orchestra-backed or Git-based storage.

Instructions

Create a new pipeline. The request body includes the pipeline definition as JSON.

Use Validate pipeline schema before creating a pipeline if you want to check the payload without saving it.

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": {
      "data": "<data>",
      "published": "<published>"
    },
    "name": "create_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesPipeline definition as JSON, matching the pipeline YAML structure (required top-level keys: version, name, pipeline). Validate it with the validate_pipeline tool before submitting.
aliasNo
folderNoFolder path for an Orchestra-backed pipeline, such as `finance/daily`. Omit it on update to keep the current folder; send null or an empty string to clear it.
messageNo
yamlPathNo
publishedYes
repositoryNo
defaultBranchNo
workingBranchNo
messageIsCustomNo
storageProviderNoORCHESTRA
X-Orchestra-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.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.10.29-0
    • addedInput schema / properties / folder
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Folder path for an Orchestra-backed pipeline, such as `finance/daily`. Omit it on update to keep the current folder; send null or an empty string to clear it."
      +}
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds only that the definition is inline JSON, and stays silent on what actually happens with the 'published' flag, how storageProvider changes behavior, or what is created when the call fails midway — meaningful gaps for a 12-param write 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?

Two short sentences, front-loaded with the core action and followed by the validation tip — no filler. The embedded markdown link to '/api/pipelines/validate-pipeline-schema' is REST-doc residue that costs the reader a hop instead of naming the validate_pipeline tool directly.

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?

Output shape is covered by an existing output schema, so the description need not describe return values. Given that, the two sentences plus the validate-first tip supply enough for an agent to make a correct first call; the depth of field semantics is a schema-authoring gap, not something this description is positioned to fix.

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 coverage is only 25%, so the description is expected to compensate, but it explains only the 'data' parameter and says nothing about alias, published, repository, defaultBranch, workingBranch, messageIsCustom, or storageProvider. An agent must infer the meaning of most of the body from bare property names, which is exactly the gap the description should fill.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Create a new pipeline') and clarifies that the pipeline definition travels in the JSON request body. That distinguishes it from read-side siblings like get_pipeline, but it never separates it from near-neighbours such as import_pipeline or update_pipeline, which an agent could easily confuse with a create.

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?

It gives one concrete precondition — run validate_pipeline first if you want to check the payload without saving — which is genuinely useful routing guidance. Beyond that, there is no statement of when create is preferred over import_pipeline, nor any note about required permissions or what to do when a pipeline with the same name exists.

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