Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updatePipeline

DestructiveIdempotent

Modify a pipeline and its stages: update existing stages by ID or create new stages by omitting ID. Owner-only access controls changes.

Instructions

Update a pipeline and its stages (owner only). Stages with id are updated, without id are created.

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": {
      "id": "<id>"
    },
    "name": "updatePipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPipeline ID
nameNoPipeline name
stagesNoStages. Include id to update an existing stage; omit id to create one.
descriptionNoPipeline description
orderWeightNoSort position

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "Pipeline description",
      +  "type": "string"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Name"New value: +"Pipeline name"
    • addedInput schema / properties / orderWeight
      Added value: +{
      +  "description": "Sort position",
      +  "type": "number"
      +}
    • addedInput schema / properties / stages
      Added value: +{
      +  "description": "Stages. Include id to update an existing stage; omit id to create one.",
      +  "items": {
      +    "properties": {
      +      "closedStage": {
      +        "description": "True if a closed stage",
      +        "type": "boolean"
      +      },
      +      "color": {
      +        "description": "Hex color, e.g. #FFFFFF",
      +        "type": "string"
      +      },
      +      "description": {
      +        "description": "Stage description",
      +        "type": "string"
      +      },
      +      "id": {
      +        "description": "Existing stage ID (update only)",
      +        "type": "number"
      +      },
      +      "name": {
      +        "description": "Stage name",
      +        "type": "string"
      +      },
      +      "orderWeight": {
      +        "description": "Sort position",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "closedStage"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "name"
      -]New value: +[
      +  "id"
      +]
  2. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the owner-only restriction, which is real context beyond the annotations, but it does not disclose the key destructive behavior an agent would need — what happens to stages omitted from the array (deletion?) or whether unspecified pipeline fields are cleared.

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 the ownership constraint front-loaded and the stage upsert rule immediately after. Nothing is redundant or padded.

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?

For a destructive bulk-ish mutation with array semantics, the definition covers the mechanics but omits the consequence for existing stages not present in the input and whether the pipeline fields are replaced or merged. Annotations and the rich schema carry much of the burden, so the gap is moderate rather than severe.

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

Parameters3/5

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

Schema coverage is 100%, so every parameter including the nested stage fields is already documented. The description restates the id-present/id-absent upsert rule that the schema's own 'stages' description also states, adding no new meaning about orderWeight, color, or closedStage.

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?

States a specific verb and resource ('Update a pipeline and its stages') and clarifies the scope extends to nested stages, which separates it from updateStage (single stage) and updatePipeline's read-only siblings. It does not explicitly contrast with createPipeline or updateStage by name, keeping it just short of a 5.

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?

The '(owner only)' note is a useful precondition, but there is no guidance on when to call this versus updatePipeline alternatives such as updateStage or createPipeline, nor on partial-update expectations. Usage is implied rather than stated.

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