Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updatePersonAttachment

DestructiveIdempotent

Update an externally hosted attachment for a person in Follow Up Boss CRM by specifying attachment ID, person ID, file URI, and file name; requires registered-system credentials.

Instructions

Update a person attachment (externally hosted file). Needs registered-system credentials (X-System headers).

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>",
      "personId": "<personId>",
      "uri": "<uri>",
      "fileName": "<fileName>"
    },
    "name": "updatePersonAttachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAttachment ID.
uriYesLink to externally hosted file.
fileNameYesFile name.
fileSizeNoSize in bytes.
personIdYesPerson ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • changedInput schema / properties / fileName / description
      Previous value: -"File name"New value: +"File name."
    • changedInput schema / properties / fileSize / description
      Previous value: -"File size"New value: +"Size in bytes."
    • changedInput schema / properties / fileSize / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / id / description
      Previous value: -"Attachment ID"New value: +"Attachment ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / personId / description
      Previous value: -"Person ID"New value: +"Person ID."
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / uri / description
      Previous value: -"File URI"New value: +"Link to externally hosted file."
  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, and the description adds genuinely new context: it requires registered-system credentials via X-System headers, which is an auth prerequisite not visible in the schema. However, it never explains what "destructive" means here – whether the prior file reference is replaced, and whether unspecified fields are cleared – which matters for a mutation flagged destructive.

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 short sentences, front-loaded with the action and resource, with the credential requirement as a secondary note. No filler, though the parenthetical and credential note read as telegraphic rather than fully formed guidance.

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 five-parameter destructive mutation with no output schema, the description covers the auth requirement but omits what the update does to existing data, what is returned, and whether the attachment must pre-exist. Adequate to call correctly, but thin on consequences for a destructive write.

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 schema already documents all five parameters, establishing a baseline of 3. The description goes slightly beyond by clarifying that the attachment is an externally hosted file, which explains why uri (a link) rather than a binary payload is required. It adds no per-parameter detail beyond that.

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+resource ("Update a person attachment") and disambiguates the resource as an externally hosted file, which distinguishes it from generic attachment edits. It does not explicitly contrast with createPersonAttachment or getPersonAttachment, but the operation 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 Guidelines2/5

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

No guidance on when to use this versus the sibling tools createPersonAttachment, getPersonAttachment, or updateDealAttachment. The only context given is the credential prerequisite, not the selection criteria or preconditions (e.g., attachment must already exist).

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