Skip to main content
Glama
gray-wilbee

fub-mcp

by gray-wilbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

post_inbox_apps_message

Adds a message to a Follow Up Boss Inbox App conversation, creating it if needed. Handles sender details, attachments, and delivery status for complete message tracking.

Instructions

Adds a message to an existing or new Inbox App conversation. (POST /inboxApps/{inboxAppId}/message)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerNoThe owner of the conversation. Can be a FUB User or FUB Team Inbox. Required on the first message in a conversation.
personNoThe person associated with the conversation. A Person ID is preferred, but name, email, and/or phone are acceptable if the person does not exist in FUB yet. Required on the first message in a conversation.
senderYesWho sent the message. Can be a FUB User, a FUB Person, or an unrelated entity such as an AI bot.
sentAtNoThe timestamp the message was delivered at in ISO8601 UTC format. Defaults to current time if omitted.
messageYesA plaintext message body.
subjectNoSets or updates the subject of the conversation.
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.
inboxAppIdYes
isIncomingYesIndicates if the message was incoming to your system.
attachmentsNo
richObjectsNoList of Rich Object URLs.
isAutomationNoWhether the sender is an automated system. Defaults to false.
deliveryStatusNoThe message's delivery status.
externalMessageIdYesA unique identifier that references this message.
externalConversationIdYesA unique identifier that references this conversation.
replyToExternalMessageIdNoIf this message is a reply to a previous message, specify the external message ID of the message being replied to.
deliveryStatusErrorMessageNoOptional user-facing error message for Not Delivered statuses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the core action and endpoint, but does not mention side effects, whether an existing conversation is updated, how new conversation creation is triggered, or any authorization or error behavior. This is a significant gap for a mutating operation.

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?

The description is a single, focused sentence that states the action and the endpoint. It is front-loaded with the core purpose and contains no filler or redundant material.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool having 18 parameters, nested objects, no output schema, and no annotations, the description gives no information about return values, expected behavior for new vs. existing conversations, or handling of required owner/person fields. It is too sparse to fully guide an agent in invoking this complex tool correctly.

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 high at 89%, so the schema already documents most parameters. The description adds minimal extra meaning beyond identifying inboxAppId as a path parameter in the endpoint URL. This meets the baseline but does not compensate for the few undocumented fields.

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 uses a specific verb and resource: 'Adds a message to an existing or new Inbox App conversation.' It also includes the endpoint path, which clarifies the operation. It does not explicitly differentiate from sibling tools like put_inbox_apps_message or post_inbox_apps_system_message, so it stops short of 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 Guidelines3/5

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

The description implies when to use the tool by saying it adds a message, but it gives no guidance on when to prefer it over the closely related put_inbox_apps_message or post_inbox_apps_note. It provides no exclusions or alternative routing, so usage guidance is only implicit.

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