Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateAppointment

DestructiveIdempotent

Update an existing Follow Up Boss CRM appointment and its invitees; supply start and end on every edit to avoid validation errors.

Instructions

Update an appointment. FUB requires start and end on EVERY update (even partial edits) or it returns 'Valid Start and End dates are required'. Refetch with getAppointment first if you only have the id. Invitees: [{userId:int}] for a FUB user, [{personId:int}] for a contact (optional name/email). The shape {type,id} is NOT FUB's; it is auto-converted, but prefer userId/personId. This tool never sends invitation emails (sendInvitation is not sent; FUB's default is off), but FUB syncs appointments to Google/Outlook calendars for invitees, so a person invitee may still get a calendar invite from the calendar side.

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

Input Schema

NameRequiredDescriptionDefault
idYesAppointment ID
endNoEnd ISO
startNoStart ISO
titleNo
allDayNo
typeIdNoType ID
inviteesNoArray of {userId:int} (FUB user) and/or {personId:int} (contact)
locationNo
outcomeIdNoOutcome ID
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / invitees / description
      Added value: +"Array of {userId:int} (FUB user) and/or {personId:int} (contact)"
  2. Changed14 schema fields changedv1.1.3
    • addedInput schema / properties / allDay
      Added value: +{
      +  "type": "boolean"
      +}
    • removedInput schema / properties / appointmentOutcomeId
      Removed value: -{
      -  "description": "Outcome ID",
      -  "type": "number"
      -}
    • removedInput schema / properties / appointmentTypeId
      Removed value: -{
      -  "description": "Type ID",
      -  "type": "number"
      -}
    • removedInput schema / properties / description / description
      Removed value: -"Description"
    • addedInput schema / properties / end
      Added value: +{
      +  "description": "End ISO",
      +  "type": "string"
      +}
    • removedInput schema / properties / endTime
      Removed value: -{
      -  "description": "End time",
      -  "type": "string"
      -}
    • removedInput schema / properties / invitees / description
      Removed value: -"Invitees"
    • removedInput schema / properties / location / description
      Removed value: -"Location"
    • addedInput schema / properties / outcomeId
      Added value: +{
      +  "description": "Outcome ID",
      +  "type": "number"
      +}
    • removedInput schema / properties / personId
      Removed value: -{
      -  "description": "Person ID",
      -  "type": "number"
      -}
    • addedInput schema / properties / start
      Added value: +{
      +  "description": "Start ISO",
      +  "type": "string"
      +}
    • removedInput schema / properties / startTime
      Removed value: -{
      -  "description": "Start time",
      -  "type": "string"
      -}
    • removedInput schema / properties / title / description
      Removed value: -"Title"
    • addedInput schema / properties / typeId
      Added value: +{
      +  "description": "Type ID",
      +  "type": "number"
      +}
  3. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

The description adds substantial behavior beyond the annotations (which already declare readOnly=false, destructive, idempotent): the FUB server-side rule that start and end are required on every update, the exact error text returned, and the invitation-email and calendar-sync side effects. That is real operational context an agent cannot get from the schema alone.

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?

It is dense and front-loads the most important constraint (start/end on every update) right after the purpose sentence. Every sentence carries information, though the invitee-shape and calendar-sync sentences are packed tightly and could read more cleanly.

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 10-parameter destructive mutation with no output schema, the description covers the highest-risk gotchas: required fields, the refetch workflow, invitee format, and notification side effects. What is missing is the response shape and any permission prerequisites, which are secondary here.

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?

With 60% schema coverage, the description compensates by spelling out the invitees contract (userId/personId vs the {type,id} shape, optional name/email) and the start/end requirement. It leaves title, allDay, typeId, location, and outcomeId to schema names, which is reasonable but not 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+resource ('Update an appointment') that is immediately distinguishable from siblings createAppointment, getAppointment, and updateAppointmentType. It stops short of explicitly contrasting itself with those siblings, but the intent 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete conditional route to a sibling: 'Refetch with getAppointment first if you only have the id.' It also tells the caller that start/end are mandatory on every update, which steers usage. It does not say when to use createAppointment instead, so it is clear but not exhaustive.

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