Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

bulkUpdatePeople

Destructive

Updates many people with the same Follow Up Boss field changes in a throttled batch, avoiding individual update loops and returning per-person success.

Instructions

Apply the same updatePerson changes to many people, throttled (pauses 11s per 20 people). Use this instead of looping updatePerson. Returns per-person success.

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": {
      "ids": "<ids>",
      "updates": "<updates>"
    },
    "name": "bulkUpdatePeople"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesPerson IDs to update.
updatesYesFields to set on each person, same as updatePerson (tags, stage, assignedUserId, custom fields).
mergeTagsNoMerge tags instead of replacing them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / properties / ids / description
      Previous value: -"Array of person IDs to update"New value: +"Person IDs to update."
    • changedInput schema / properties / ids / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / mergeTags / description
      Previous value: -"Merge tags instead of replacing"New value: +"Merge tags instead of replacing them."
    • changedInput schema / properties / updates / description
      Previous value: -"Fields to update on each person (same fields as updatePerson: tags, stage, assignedTo, custom* fields, etc.)"New value: +"Fields to set on each person, same as updatePerson (tags, stage, assignedUserId, custom fields)."
  2. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / updates / description
      Previous value: -"Fields to update on each person (same fields as updatePerson: tags, stage, assignedTo, etc.)"New value: +"Fields to update on each person (same fields as updatePerson: tags, stage, assignedTo, custom* fields, etc.)"
  3. First observedv1.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false. The description adds genuinely new behavioral context the annotations cannot carry: a concrete throttling cost ('pauses 11s per 20 people') and the return shape ('per-person success'). It does not say whether a single failure aborts the batch, which is the main remaining behavioral gap for a bulk mutation.

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 tight sentences with no waste: the action and replacement relationship come first, the throttling cost and return value follow. Every clause earns its place and nothing is restated from the schema.

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 three-parameter bulk mutation with no output schema, the definition covers what it does, the cost of calling it, and what comes back. The gaps are partial-failure semantics and whether pre-existing values are overwritten, though the destructiveHint annotation and mergeTags option partially signal the overwrite behavior.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3 and the schema already explains ids, updates, and mergeTags. The description adds meaning beyond the schema by tying the 'updates' object to updatePerson's field set, giving the agent a cross-tool reference for an otherwise opaque nested object.

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

Purpose5/5

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

States a specific verb and resource ('Apply the same updatePerson changes to many people') and bounds the semantics by referencing the sibling updatePerson, so an agent knows exactly what field set applies. It is clearly distinguished from the single-record updatePerson tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicit routing guidance: 'Use this instead of looping updatePerson' names the alternative and the condition that selects this tool. It stops short of stating when to prefer updatePerson (single-record, non-throttled case), which is easily inferred but not spelled out.

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