Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createPipeline

Creates a sales pipeline with optional stages so account owners can organize deals and define which stages are closed.

Instructions

Create a pipeline with optional stages (account owner only). Each stage needs name and closedStage.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPipeline 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. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "Pipeline description",
      +  "type": "string"
      +}
    • 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"
      +}
  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 readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write semantics are covered structurally. The description adds the account-owner authorization constraint, which is genuinely useful context, but says nothing about failure behavior, duplicate-name handling, or what is returned.

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 with the authorization constraint and the nested-field requirement front-loaded. Nothing is wasted, though the second sentence largely echoes what the schema's required arrays already enforce.

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?

For a simple 4-parameter create tool with no output schema and full schema coverage, the description covers purpose, permission scope, and nested stage structure. Only the return value and the effect of omitting stages entirely are left unstated.

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 in the schema. The description's "Each stage needs name and closedStage" restates the nested required array rather than adding format or constraint detail, so baseline 3 applies.

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?

"Create a pipeline" states a specific verb and resource, and the parenthetical scopes it to optional stages. It is distinguishable from listPipelines/getPipeline/updatePipeline by the verb alone, though it never names those siblings explicitly.

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?

"account owner only" gives a real prerequisite that affects whether an agent can call it at all. However, there is no guidance on when to use this versus updatePipeline (e.g. modifying an existing pipeline) or on whether stages can be added later via createStage.

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