Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateNote

DestructiveIdempotent

Modify an existing Follow Up Boss CRM note by sending only the fields to change, such as subject, body, HTML rendering, or linked person.

Instructions

Update a note. Send only fields to change.

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

Input Schema

NameRequiredDescriptionDefault
idYesNote ID.
bodyNoNote content.
isHtmlNotrue = render HTML tags in body.
subjectNoNote title.
personIdNoPerson the note belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.0
    • changedInput schema / properties / body / description
      Previous value: -"Updated note body"New value: +"Note content."
    • changedInput schema / properties / id / description
      Previous value: -"Note ID"New value: +"Note ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / isHtml
      Added value: +{
      +  "description": "true = render HTML tags in body.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / personId
      Added value: +{
      +  "description": "Person the note belongs to.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / subject
      Added value: +{
      +  "description": "Note title.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "body"
      -]New value: +[
      +  "id"
      +]
  2. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond them: this is a partial/PATCH-style update where omitted fields are left alone. It says nothing about what destruction is possible, permission needs, or error behavior.

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, zero filler, and the partial-update rule is front-loaded right after the purpose statement. Nothing is wasted.

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 5-parameter update tool with a fully documented schema and no output schema, the essentials are present. However, given the destructive hint is set and no return value is described, the description could say whether the updated note is returned or whether isHtml defaulting affects body interpretation.

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 every parameter including body, isHtml, subject and personId is already documented in the schema. "Send only fields to change" reinforces the partial-update contract that the optionality of the schema only implies, but adds no syntax, format, or validation detail. Baseline 3 applies.

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?

"Update a note" states a specific verb and resource, so an agent immediately knows this is the mutation counterpart to getNote/createNote. It does not explicitly name those siblings or distinguish itself from inboxAppUpdateMessage-style alternatives, which keeps it below 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 Guidelines2/5

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

The only guidance is "Send only fields to change," which describes how to call it rather than when to use it over alternatives such as createNote or updatePerson. No prerequisites, no mention of needing an existing note id, no 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