Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateTeam

DestructiveIdempotent

Update a team's name, description, members, and leaders by ID; when sending user or leader IDs, provide the complete replacement list.

Instructions

Update a team by ID. If userIds or leaderIds is sent, send the COMPLETE list; it replaces the existing one.

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

Input Schema

NameRequiredDescriptionDefault
idYesTeam ID.
nameNoName of the team.
userIdsNoComplete list of member user IDs.
leaderIdsNoComplete list of team leader user IDs.
descriptionNoTeam description (not in FUB docs; may be ignored).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.0
    • changedInput schema / properties / description / description
      Previous value: -"Description"New value: +"Team description (not in FUB docs; may be ignored)."
    • changedInput schema / properties / id / description
      Previous value: -"Team ID"New value: +"Team ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • 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: -"Name"New value: +"Name of the team."
    • addedInput schema / properties / userIds
      Added value: +{
      +  "description": "Complete list of member user IDs.",
      +  "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?

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description earns credit by explaining the mechanism of the destruction: list-valued fields replace rather than merge, which is exactly the failure mode an agent would otherwise hit. It still does not spell out permissions or what happens to fields left absent.

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 short sentences with no filler. The identification of the resource comes first and the high-risk replacement warning is front-loaded in the second sentence where an agent will read it before constructing arguments.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter update tool with full schema coverage and annotations carrying the safety hints, the description covers the one non-obvious behavior an agent must know. No output schema needs explaining, and the only unmentioned aspect, the possibly-ignored description field, is already flagged in the schema.

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 description coverage is 100%, so the baseline is 3. The description adds real meaning beyond that baseline by stating the replace-not-append semantics for userIds and leaderIds, which the schema only hints at with the word 'Complete'.

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 and resource, 'Update a team by ID', which is unambiguous and lets an agent separate it from createTeam, getTeam, and listTeams. It does not explicitly name sibling alternatives, 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?

There is no explicit statement of when to use this tool versus createTeam or getTeam, and no prerequisites or exclusions are given. However, the conditional 'If userIds or leaderIds is sent, send the COMPLETE list' functions as operational guidance for how to invoke it correctly, which lifts it above the bare minimum.

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