Skip to main content
Glama
gray-wilbee

fub-mcp

by gray-wilbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_text_message

Record an external text message in Follow Up Boss CRM and link it to a person by ID, storing message body, from/to phone numbers, and optional timeline details.

Instructions

Create a record of an externally sent text message. (POST /textMessages)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesThe body of the text message.
personIdYesThe id of the person associated with the text message.
toNumberYesThe phone number the text message was sent to (e.g., 888-555-1234).
extraBodyNoExtra raw JSON body fields not explicitly listed above — e.g. custom.* fields when creating/updating people or deals. Keys and values are sent as-is.
extraQueryNoExtra raw query parameters not explicitly listed above — e.g. FUB custom field filters like custom.ClosingDate on /people or /deals. Keys and values are sent as-is.
fromNumberYesThe phone number the text messages was sent from (e.g., 888-555-9876).
isIncomingNoSet whether the text was outgoing to a person or incoming from a person.
externalUrlNoAn optional link that will appear in the byline of the text message record in the timeline.
externalLabelNoAn optional descriptive text that appears in the byline of the text message record on the person's timeline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. 'Create a record' makes the primary side effect clear and 'externally sent' suggests no actual SMS is dispatched by this tool. But it does not address permissions, error behavior, or what happens with incoming messages despite the isIncoming parameter.

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?

One sentence with no wasted words, and the essential purpose is front-loaded. Including the POST path is a compact way to ground the tool in the API surface.

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?

The tool is a 9-parameter creation action, and the schema covers parameters well, so the description is minimally sufficient. However, it omits any mention of return value or response behavior, and there is no output schema to compensate, leaving some ambiguity about what the caller should expect.

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 fully documents all parameters. The description adds no extra meaning about parameter formats, relationships, or usage beyond what the schema already provides, which meets the baseline but does not add value.

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?

The description uses a specific verb and resource: 'Create a record of an externally sent text message', and includes the POST /textMessages endpoint. This clearly distinguishes the tool from siblings like list_text_messages, get_text_message, and create_text_message_template.

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?

The phrase 'externally sent text message' implies this tool is for logging texts that were sent outside the system rather than for sending new texts. However, it does not explicitly state when to prefer this tool over get_text_message or create_text_message_template, and it offers 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