Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateTask

DestructiveIdempotent

Modify a Follow Up Boss task's details, due date or assignment, and mark it completed. Set deadlines by date or exact time with optional reminders.

Instructions

Update a task. Mark done with isCompleted=true. dueDate is YYYY-MM-DD; use dueDateTime for a specific time.

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

Input Schema

NameRequiredDescriptionDefault
idYesTask ID
nameNoTask name
typeNoTask category
dueDateNoDue date, YYYY-MM-DD
personIdNoPerson the task relates to
assignedToNoFull name of the user to assign
dueDateTimeNoDue date-time with optional offset, e.g. 2026-11-02T15:00:00-05:00
isCompletedNoMark completed or not
assignedUserIdNoUser ID to assign
remindSecondsBeforeNoReminder lead time in seconds; only for tasks with a due time

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.0.0
    • addedInput schema / properties / assignedTo
      Added value: +{
      +  "description": "Full name of the user to assign",
      +  "type": "string"
      +}
    • changedInput schema / properties / assignedUserId / description
      Previous value: -"Assigned user"New value: +"User ID to assign"
    • changedInput schema / properties / dueDate / description
      Previous value: -"Due date"New value: +"Due date, YYYY-MM-DD"
    • addedInput schema / properties / dueDateTime
      Added value: +{
      +  "description": "Due date-time with optional offset, e.g. 2026-11-02T15:00:00-05:00",
      +  "type": "string"
      +}
    • addedInput schema / properties / isCompleted
      Added value: +{
      +  "description": "Mark completed or not",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Name"New value: +"Task name"
    • changedInput schema / properties / personId / description
      Previous value: -"Person ID"New value: +"Person the task relates to"
    • addedInput schema / properties / remindSecondsBefore
      Added value: +{
      +  "description": "Reminder lead time in seconds; only for tasks with a due time",
      +  "type": "number"
      +}
    • removedInput schema / properties / status
      Removed value: -{
      -  "description": "Status",
      -  "type": "string"
      -}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Task category",
      +  "enum": [
      +    "Follow Up",
      +    "Call",
      +    "Email",
      +    "Text",
      +    "Appointment",
      +    "Showing",
      +    "Closing",
      +    "Open House",
      +    "Thank You"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, idempotentHint=true and a non-read-only tool, so the description should clarify what can be destroyed. It never says whether omitted fields are left untouched or cleared, nor whether the update is a full replace; with a destructive mutation and 10 parameters, this is a significant undisclosed trait.

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, front-loaded sentences with no filler. Every clause carries actionable information and nothing is redundant.

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

Completeness2/5

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

For a 10-parameter destructive mutation with no output schema, the description is too thin: partial-update semantics, the meaning of the destructive hint, and the required id are all left unaddressed. The tool is callable, but an agent cannot predict the side effects of omitting fields.

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 documents every parameter and the 3 baseline applies. The description adds only marginal value by clarifying the dueDate versus dueDateTime choice for specifying a time; it says nothing about id requirements, assignedTo vs assignedUserId precedence, or remindSecondsBefore constraints.

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?

States a specific verb and resource ('Update a task') and immediately names a concrete operation it enables ('Mark done with isCompleted=true'). It does not explicitly differentiate itself from siblings like createTask, getTask, or listTasks, but the verb+resource combination is unambiguous.

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?

Offers conditional guidance for two fields ('use dueDateTime for a specific time'), which implicitly tells the agent which parameter to pick. However, there is no guidance on when to call updateTask versus createTask/getTask, no prerequisites (e.g., needing an existing id), and no mention of what happens on a partial update.

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