Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createStage

Create a new pipeline stage in Follow Up Boss CRM by name, with an optional sort position. Order weight defaults to 1000 and stages are renumbered in steps of 1000.

Instructions

Create a stage. orderWeight defaults to 1000; FUB then renumbers all stages in steps of 1000.

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": "createStage"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesStage name
orderWeightNoSort position. Default 1000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / orderWeight
      Added value: +{
      +  "description": "Sort position. Default 1000",
      +  "type": "number"
      +}
    • removedInput schema / properties / pipelineId
      Removed value: -{
      -  "description": "Pipeline ID",
      -  "type": "number"
      -}
  2. First observedv1.1.1

TDQS

A3.6/5.0
Behavior4/5

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

The annotations mark this as a non-read-only, non-destructive, non-idempotent write, and the description adds meaningful context: orderWeight defaults to 1000 and the backend renumbers all stages in increments of 1000. That side effect on other records is disclosed behavior beyond the annotations. It still lacks details on permissions or failure modes.

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 core action front-loaded and the behavioral footnote second. No padding or redundant phrasing.

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?

This is a simple two-parameter create tool with no output schema, and the description covers the action and the notable ordering side effect. It does not explain the result of creation, such as a returned stage ID, or relationships to pipelines, but that gap is minor for this complexity.

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 both parameters are already documented, including the default of 1000 for orderWeight. The description restates that default and adds only the renumbering consequence, so it adds marginal value over the schema. A 3 baseline is appropriate.

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 opens with a specific verb and resource: "Create a stage." That is unambiguous. However, it does not distinguish this tool from siblings like createPipeline or updateStage, nor does it say which entity the stage belongs to, so it falls short of the sibling differentiation seen in 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 Guidelines2/5

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

There is no guidance about when to use this tool versus updateStage or createPipeline, and no prerequisites or exclusions are stated. The agent must infer that this is the creation path for pipeline stages from the name alone.

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