Skip to main content
Glama

Upsert project pipeline

upsert_project_pipeline

Create or update a project pipeline, configuring environments, variables, sync modes, and deployment roles for automated releases.

Instructions

Create or edit one project-level pipeline through the local agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNo
serviceNoService config. Set service.language (go, node, python) as the service implementation language; it is required for local managed runtime.type=language deployments. For remote deployments, deployments[].host_ids must contain canonical non-self Host.id values returned by list_hosts, not host name/display name. Set deployments[].ports (array of ints) to declare the ports a deployment listens on; for a project homed on a dev machine this is what makes SuperDev mirror those ports back to 127.0.0.1 on the control-plane machine.
pipelineYesProject pipeline config. Key fields: `variables` are pipeline-wide defaults (strings). `environments` is a map of env name -> { variables } that OVERRIDE defaults per environment (precedence: project < pipeline < pipeline.pipeline < environments[env] < run vars); the same pipeline serves multiple environments by overriding only the differing variables. `sync_mode` declares how build artifacts reach targets: "transfer" (agent uploads the packaged artifact) or "remote_cmd" (the target host runs a command such as git pull to fetch code itself); empty defaults to transfer. `roles` maps a role/run-group name to a host list (run groups); a role entry uses {from_service} to derive hosts from a service's deployment for the running env, or {hosts:[...]} for an explicit set. Only plugins that need to target a specific group (e.g. nginx upstream) reference roles; most deploy steps follow the env deployment targets automatically. Any host_ids, roles hosts, or task host_id values must use canonical non-self Host.id values returned by list_hosts, not host names.
root_pathNo
project_idNo
project_nameNo
approval_tokenNo
debug_session_idNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.2.4
    • changedInput schema / properties / service / description
      Previous value: -"Service config. Set service.language (go, node, python) as the service implementation language; it is required for local managed runtime.type=language deployments. For remote deployments, deployments[].host_ids must contain canonical non-self Host.id values returned by list_hosts, not host name/display name."New value: +"Service config. Set service.language (go, node, python) as the service implementation language; it is required for local managed runtime.type=language deployments. For remote deployments, deployments[].host_ids must contain canonical non-self Host.id values returned by list_hosts, not host name/display name. Set deployments[].ports (array of ints) to declare the ports a deployment listens on; for a project homed on a dev machine this is what makes SuperDev mirror those ports back to 127.0.0.1 on the control-plane machine."
  2. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the mutation ('create or edit') but does not disclose idempotency details, whether it overwrites existing configuration, potential side effects on other resources, or required permissions. The nested schema descriptions cover some behavior (e.g., variable precedence), but those are not visible in the tool description itself.

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 description is a single, concise sentence with no fluff. It communicates the core action without redundancy, earning high marks for conciseness. However, being extremely terse leaves out critical context, so it doesn't reach a 5.

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

Completeness2/5

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

For a tool with nested objects and a rich schema, the description is inadequate. It does not explain return values (though no output schema is provided), side effects, error conditions, or prerequisites. An agent would need to dive into the schema to understand even basic usage, and the 6 undocumented parameters make it even more challenging. The description offers no safety net for a complex operation like an upsert.

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 only 25% (2 of 8 parameters described), and the tool description adds no parameter-level information. The description mentions 'project-level pipeline' but does not explain the six undocumented parameters (e.g., project_id, root_path, approval_token). The schema's own descriptions for 'service' and 'pipeline' provide substantial meaning, but they are part of the input schema, not the tool description, and the remaining parameters remain opaque.

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 uses a clear verb ('Create or edit') and identifies the resource ('one project-level pipeline'), which effectively distinguishes this from siblings like 'deploy_project_pipeline' or 'upsert_project_config'. The phrase 'through the local agent' provides context about the execution medium. It is specific enough that an agent can infer the primary purpose, though it doesn't name alternatives explicitly.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus its siblings, such as when to prefer this over 'upsert_project_config' or 'validate_project_pipeline'. The only hint is 'through the local agent,' which is not elaborated. No exclusions, prerequisites, or alternative conditions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Xsxdot/super-dev'

If you have feedback or need assistance with the MCP directory API, please join our Discord server