Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateAutomationPerson

DestructiveIdempotent

Pause or resume a person within a Follow Up Boss automation by setting their status to Paused or Running, using the automation person ID.

Instructions

Pause or resume a person in an automation. Needs registered-system credentials.

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

Input Schema

NameRequiredDescriptionDefault
idYesAutomationPerson ID.
statusNoPaused pauses; Running resumes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / properties / id / description
      Previous value: -"AutomationPerson ID"New value: +"AutomationPerson ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / status / description
      Previous value: -"New status"New value: +"Paused pauses; Running resumes."
    • addedInput schema / properties / status / enum
      Added value: +[
      +  "Running",
      +  "Paused"
      +]
  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, idempotentHint=true and readOnlyHint=false; the description adds the auth requirement (registered-system credentials), which is genuinely useful context not in the annotations. However, it never explains what the destructive aspect means — whether the person is removed from the automation run, whether state is lost, or whether the change is reversible.

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, zero redundancy, with the action front-loaded and the prerequisite trailing. Nothing could be cut without losing information.

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 two-parameter mutation tool with no output schema, the description covers purpose and a credential prerequisite, which is the minimum an agent needs. It is still thin on effect semantics — what happens to the person's automation state and what a successful response looks like.

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% and the enum property already documents 'Paused pauses; Running resumes', so the description adds no meaning beyond the schema. It also says nothing about the required id or about the default when status is omitted. Baseline 3 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 states a specific verb pair (pause/resume) and a specific resource (a person in an automation), which separates it from siblings like updateActionPlanPerson and addPersonToAutomation. It does not explicitly name a sibling alternative, but the resource boundary is clear enough to select correctly.

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?

'Pause or resume a person in an automation' implies the usage context, and the credential prerequisite is surfaced. There is no explicit when-not guidance or reference to getAutomationPerson/addPersonToAutomation for related operations, so routing is only implied.

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