Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateGroup

DestructiveIdempotent

Modify an existing Follow Up Boss group by ID, changing only the fields you send. Keeps current members when users is omitted; requires admin access.

Instructions

Update a group by ID. Admin accounts only. Send only fields to change; the current users are kept when users is not sent.

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

Input Schema

NameRequiredDescriptionDefault
idYesGroup ID.
nameNoName of the group.
typeNoGroup type. FUB default Agent.
usersNoUser IDs that are members of this group. Required by FUB.
claimWindowNoSeconds to claim a lead in a first-to-claim group, 1 to 30 minutes. FUB default 1800.
distributionNoDistribution model. Lender groups cannot be first-to-claim. FUB default round-robin.
defaultPondIdNoPond that gets unclaimed first-to-claim leads after the claim window.
defaultUserIdNoUser who gets unclaimed first-to-claim leads after the claim window.
defaultGroupIdNoGroup that gets unclaimed first-to-claim leads after the claim window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv2.0.0
    • addedInput schema / properties / claimWindow
      Added value: +{
      +  "description": "Seconds to claim a lead in a first-to-claim group, 1 to 30 minutes. FUB default 1800.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / defaultGroupId
      Added value: +{
      +  "description": "Group that gets unclaimed first-to-claim leads after the claim window.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / defaultPondId
      Added value: +{
      +  "description": "Pond that gets unclaimed first-to-claim leads after the claim window.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / defaultUserId
      Added value: +{
      +  "description": "User who gets unclaimed first-to-claim leads after the claim window.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / distribution
      Added value: +{
      +  "description": "Distribution model. Lender groups cannot be first-to-claim. FUB default round-robin.",
      +  "enum": [
      +    "first-to-claim",
      +    "round-robin"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / id / description
      Previous value: -"Group ID"New value: +"Group ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / name / description
      Previous value: -"Name"New value: +"Name of the group."
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Group type. FUB default Agent.",
      +  "enum": [
      +    "Agent",
      +    "Lender"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / userIds
      Removed value: -{
      -  "description": "User IDs",
      -  "items": {
      -    "type": "number"
      -  },
      -  "type": "array"
      -}
    • addedInput schema / properties / users
      Added value: +{
      +  "description": "User IDs that are members of this group. Required by FUB.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
  2. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds genuinely useful context beyond them: the admin-only authorization requirement and the replace-on-send semantics of the users field ('the current users are kept when users is not sent'), which is exactly the behavior an agent needs to know before touching a destructive field. It does not spell out that passing a users list overwrites existing membership wholesale, nor how claimWindow/distribution interact, leaving some destructive consequences implicit.

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?

Three short sentences, front-loaded with the action and identifier, then permission scope, then the partial-update rule. No filler and every sentence carries actionable information.

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 nine-parameter destructive mutation with no output schema, the description covers the essentials: identifier-based targeting, admin auth, and patch-vs-replace behavior for the riskiest field. It lacks detail on what the response returns and on how the claim/distribution defaults are applied when omitted, which is a minor gap given the schema already documents defaults.

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 description coverage is 100%, so the schema already carries per-field meaning and defaults for all nine parameters; the baseline of 3 applies. The description does add one non-obvious semantic rule about users being retained when omitted, but otherwise adds no meaning beyond the schema's field documentation.

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+resource ('Update a group by ID'), which is unambiguous and distinguishable from sibling read/create tools like getGroup and createGroup. It does not explicitly contrast with near-neighbors such as updateTeam or updatePond, so it stops short of full sibling differentiation.

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?

It states a real prerequisite ('Admin accounts only') and gives clear guidance on how to call it ('Send only fields to change'), which is the key usage pattern for a partial update. It does not say when to prefer this over updateTeam/updatePond or when a group update is inappropriate, so alternatives are left implicit.

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