Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createPersonAttachment

Attach an externally hosted file to a person in Follow Up Boss CRM with person ID, file URI, and file name; use it to link documents to contact records.

Instructions

Attach an externally-hosted file to a person. "Restricted - Registered Systems Only": requires FUB_SYSTEM + FUB_SYSTEM_KEY env vars. uri must point to an externally hosted file — FUB does NOT host uploads via this endpoint (omitting URI returns 403).

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

Input Schema

NameRequiredDescriptionDefault
uriYesFile URI
fileNameYesFile name
fileSizeNoFile size in bytes
personIdYesPerson ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-readOnly, non-destructive, non-idempotent mutation; the description adds the parts annotations cannot express: an auth/registration gate via env vars, the 403 failure mode, and the critical constraint that FUB does not host uploads. It still doesn't say whether attaching the same URI twice duplicates the record, which matters given idempotentHint=false.

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?

Three short sentences with the core action front-loaded and the constraint detail after it; no filler. The quoted "Restricted - Registered Systems Only" label is slightly awkward but it does carry the gating information compactly.

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 4-parameter mutation with annotations covering the safety profile and no output schema, the description covers what an agent most needs: auth requirements, the external-hosting rule, and the 403 outcome. Missing only secondary operational detail such as accepted file types, size limits, and duplicate-attachment behavior.

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 the schema already names all four parameters, and the baseline is 3. The description does add real meaning for `uri` beyond "File URI" — it must point to an externally hosted file, not a FUB-hosted upload — but says nothing about fileName, fileSize, or personId.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Attach an externally-hosted file to a person"), which immediately separates it from the deal-attachment and person-CRUD siblings like createDealAttachment and updatePersonAttachment. The externally-hosted qualifier further narrows the scope before the agent reads any schema.

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?

Gives explicit prerequisites: it is restricted to registered systems and needs FUB_SYSTEM plus FUB_SYSTEM_KEY env vars, and it warns that a missing URI returns 403. It does not name a sibling alternative (e.g., when to prefer updatePersonAttachment), so it stops short of full when/when-not routing.

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