Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createGroup

Create a lead-routing group for Follow Up Boss admin accounts by specifying a name and member user IDs, with options for distribution, claim windows, and fallback routing.

Instructions

Create a lead-routing group. Admin accounts only. name and users (user IDs) are required; the member list key is users, not userIds.

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>",
      "users": "<users>"
    },
    "name": "createGroup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the group.
typeNoGroup type. FUB default Agent.
usersYesUser 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. Changed10 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 / name / description
      Previous value: -"Group 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"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[
      +  "name",
      +  "users"
      +]
  2. 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 a non-read-only, non-destructive, non-idempotent mutation, so the safety profile is covered; the description adds the admin-authorization gate, which annotations cannot express. It does not disclose duplicate-name behavior or what happens to unclaimed-lead defaults when distribution is omitted, leaving some mutation side effects unstated.

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, then the access constraint, then the parameter pitfall. Nothing is padded and the most error-prone detail is stated last for emphasis.

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 an 8-parameter mutation with no output schema, the description covers the action, the auth gate, and the required fields, and the schema carries all parameter semantics. The remaining gap is the return value — an agent is not told whether the created group (and its ID) comes back, which matters for chaining into updateGroup.

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, but the description earns an extra point by flagging the concrete trap that the member list key is "users" and not "userIds", plus clarifying that values are user IDs. It does not touch the behavioral coupling of claimWindow/distribution/default* parameters, which the schema only partly conveys.

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?

Uses a specific verb and resource ("Create a lead-routing group") and adds domain framing (lead routing) that separates it cleanly from getGroup, updateGroup, and listGroups in the sibling list. An agent can pick this tool without opening the schema.

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?

"Admin accounts only" gives an explicit precondition for use, which is real guidance rather than implication. It stops short of naming when to prefer updateGroup or how to handle an existing group with the same name, so it is clear context without full alternatives/exclusions.

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