Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateActionPlanPerson

DestructiveIdempotent

Updates a person's action plan status by ID in Follow Up Boss, enabling you to track or adjust workflow progress.

Instructions

Update a person's action plan status

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

Input Schema

NameRequiredDescriptionDefault
idYesActionPlanPerson ID
statusNoNew status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, which sets a low burden; the description nonetheless adds nothing. It does not say what the destructive aspect affects (does changing status remove the person from the plan, reset progress, trigger automation?), nor whether prior status is recoverable. For a destructive mutation this is a meaningful omission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single short sentence is front-loaded and free of padding, so it is concise. However, brevity here comes at the cost of specification rather than through efficiency, leaving the sentence with little informational payload.

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 destructive, non-read-only mutation with no output schema and a free-form status string, the description should at minimum hint at valid status values and the effect of the change; it does neither. An agent cannot confidently invoke this without guessing what values are accepted and what the call destroys.

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 documented in the schema itself and the baseline of 3 applies. The description restates "status" but adds no meaning beyond "New status" — notably it does not enumerate valid status values, and there is no enum in the schema to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update a person's action plan status" names a verb and resource, but the object (ActionPlanPerson) and the concept of "status" are never explained, and nothing distinguishes it from nearby siblings such as updateAutomationPerson or addPersonToActionPlan. An agent can guess this mutates a status field, but not which entity model it operates on.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The closest siblings (addPersonToActionPlan, updateAutomationPerson, listActionPlansPeople) are never referenced, so selecting this tool over them is pure inference.

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