Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createTeam

Creates a team in Follow Up Boss CRM with a name, member user IDs, and optional leader IDs; requires team access.

Instructions

Create a team. name and userIds (all member user IDs) are required; leaderIds is the complete list of team leaders. Needs team access (403 otherwise).

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>",
      "userIds": "<userIds>"
    },
    "name": "createTeam"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the team.
userIdsYesUser IDs that are members of the team.
leaderIdsNoComplete list of team leader user IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • removedInput schema / properties / description
      Removed value: -{
      -  "description": "Team description",
      -  "type": "string"
      -}
    • addedInput schema / properties / leaderIds
      Added value: +{
      +  "description": "Complete list of team leader user IDs.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Team name"New value: +"Name of the team."
    • addedInput schema / properties / userIds
      Added value: +{
      +  "description": "User IDs that are members of the team.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[
      +  "name",
      +  "userIds"
      +]
  2. First observedv1.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare non-read-only, non-destructive, non-idempotent, closed-world, so the safety profile is already covered. The description adds genuinely new behavioral context: the access prerequisite and the concrete 403 failure mode. It omits what happens on duplicate names and the return payload, which keeps it short of a 5.

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

Conciseness4/5

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

Two sentences, front-loaded with the action, then constraints, then the access requirement. Nothing is redundant, though the dense semicolon-clause style packs three distinct facts into one sentence and slightly reduces scannability.

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 simple three-parameter create with full schema coverage and no output schema, the description covers the essentials plus the permission failure. However, given idempotentHint=false, it should warn that repeat calls create additional teams, and it leaves the leader/member relationship unstated.

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 all three parameters are already documented, including the "complete list" wording for leaderIds. The description mostly restates those semantics ("all member user IDs", "complete list of team leaders") rather than adding new meaning such as whether a leader must also appear in userIds. 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?

"Create a team" gives a specific verb and resource, immediately distinguishing it from getTeam/updateTeam/listTeams. It does not distinguish it from near-neighbors like createGroup or createPond, which an agent might confuse it with, so it stops short of a 5.

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?

The description states the required inputs and the access prerequisite (403 without team access), which implicitly frames when the call will succeed. It offers no explicit when-to-use guidance versus createGroup/createPond, and no exclusion conditions beyond the permission failure.

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