Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

inboxAppAddMessage

Add a message to an inbox app conversation and create it automatically on first use. Key conversations by externalConversationId and include person and owner on the initial message.

Instructions

Add a message to an inbox app conversation (creates the conversation on first use). Conversations are keyed by YOUR externalConversationId. person and owner are needed on the first message of a conversation.

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": {
      "inboxAppId": "<inboxAppId>",
      "externalConversationId": "<externalConversationId>",
      "externalMessageId": "<externalMessageId>",
      "message": "<message>",
      "isIncoming": "<isIncoming>",
      "sender": "<sender>"
    },
    "name": "inboxAppAddMessage"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNoConversation owner. Needed on the first message. Set userId OR inboxId, not both.
personNoPerson on the conversation. Needed on the first message.
senderYesMessage sender. Set one of userId, personId, relationshipId, participantId, or name/email/phone.
sentAtNoDelivery time, ISO 8601 UTC. Defaults to now.
messageYesPlain-text message body.
subjectNoSets or updates the conversation subject.
inboxAppIdYesID of the inbox app making the call.
isIncomingYesTrue if the message came in to your system.
attachmentsNoAttachments; each url must stay valid at least 20 minutes.
richObjectsNoRich Object URLs.
isAutomationNoTrue if the sender is an automated system. Default false.
deliveryStatusNoDelivery status.
externalMessageIdYesYour unique ID for the message.
externalConversationIdYesYour unique ID for the conversation.
replyToExternalMessageIdNoExternal ID of the message being replied to.
deliveryStatusErrorMessageNoUser-facing error text for Not Delivered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv2.0.0
    • addedInput schema / properties / attachments
      Added value: +{
      +  "description": "Attachments; each url must stay valid at least 20 minutes.",
      +  "items": {
      +    "properties": {
      +      "filename": {
      +        "description": "File name, e.g. house.jpg.",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Attachment URL.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / conversationId
      Removed value: -{
      -  "description": "Conversation ID",
      -  "type": "string"
      -}
    • addedInput schema / properties / deliveryStatus
      Added value: +{
      +  "description": "Delivery status.",
      +  "enum": [
      +    "Sent",
      +    "Delivered",
      +    "Read",
      +    "Not Delivered"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / deliveryStatusErrorMessage
      Added value: +{
      +  "description": "User-facing error text for Not Delivered.",
      +  "type": "string"
      +}
    • addedInput schema / properties / externalConversationId
      Added value: +{
      +  "description": "Your unique ID for the conversation.",
      +  "type": "string"
      +}
    • addedInput schema / properties / externalMessageId
      Added value: +{
      +  "description": "Your unique ID for the message.",
      +  "type": "string"
      +}
    • addedInput schema / properties / inboxAppId
      Added value: +{
      +  "description": "ID of the inbox app making the call.",
      +  "type": "string"
      +}
    • addedInput schema / properties / isAutomation
      Added value: +{
      +  "description": "True if the sender is an automated system. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / isIncoming
      Added value: +{
      +  "description": "True if the message came in to your system.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / message / description
      Previous value: -"Message content"New value: +"Plain-text message body."
    • addedInput schema / properties / owner
      Added value: +{
      +  "description": "Conversation owner. Needed on the first message. Set userId OR inboxId, not both.",
      +  "properties": {
      +    "inboxId": {
      +      "description": "FUB Team Inbox that owns the conversation.",
      +      "type": "string"
      +    },
      +    "userId": {
      +      "description": "FUB User who owns the conversation.",
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / person
      Added value: +{
      +  "description": "Person on the conversation. Needed on the first message.",
      +  "properties": {
      +    "email": {
      +      "description": "Email, for people not yet in FUB.",
      +      "type": "string"
      +    },
      +    "id": {
      +      "description": "FUB Person ID.",
      +      "type": "integer"
      +    },
      +    "name": {
      +      "description": "Name, for people not yet in FUB.",
      +      "type": "string"
      +    },
      +    "phone": {
      +      "description": "Phone, for people not yet in FUB.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / replyToExternalMessageId
      Added value: +{
      +  "description": "External ID of the message being replied to.",
      +  "type": "string"
      +}
    • addedInput schema / properties / richObjects
      Added value: +{
      +  "description": "Rich Object URLs.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / sender / description
      Previous value: -"Sender info"New value: +"Message sender. Set one of userId, personId, relationshipId, participantId, or name/email/phone."
    • addedInput schema / properties / sender / properties
      Added value: +{
      +  "email": {
      +    "description": "Sender email if no ID is known.",
      +    "type": "string"
      +  },
      +  "name": {
      +    "description": "Sender name if no ID is known.",
      +    "type": "string"
      +  },
      +  "participantId": {
      +    "description": "Conversation participant ID.",
      +    "type": "integer"
      +  },
      +  "personId": {
      +    "description": "FUB Person ID.",
      +    "type": "integer"
      +  },
      +  "phone": {
      +    "description": "Sender phone if no ID is known.",
      +    "type": "string"
      +  },
      +  "relationshipId": {
      +    "description": "FUB Relationship ID.",
      +    "type": "integer"
      +  },
      +  "userId": {
      +    "description": "FUB User ID.",
      +    "type": "integer"
      +  }
      +}
    • addedInput schema / properties / sentAt
      Added value: +{
      +  "description": "Delivery time, ISO 8601 UTC. Defaults to now.",
      +  "type": "string"
      +}
    • addedInput schema / properties / subject
      Added value: +{
      +  "description": "Sets or updates the conversation subject.",
      +  "type": "string"
      +}
    • removedInput schema / properties / timestamp
      Removed value: -{
      -  "description": "ISO timestamp",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "conversationId",
      -  "message"
      -]New value: +[
      +  "inboxAppId",
      +  "externalConversationId",
      +  "externalMessageId",
      +  "message",
      +  "isIncoming",
      +  "sender"
      +]
  2. First observedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, but the description contributes information the annotations cannot: this call has a creation side effect that spins up a conversation, and that conversation is keyed by the caller's externalConversationId. It does not cover duplicate externalMessageId handling or failure modes, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short clauses, each carrying a distinct fact (what it does, creation side effect, keying rule, first-message requirements), with the core action front-loaded. No filler or restated title.

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 16-parameter mutation with nested person/owner/sender objects and no output schema, the description covers the essential creation semantics but leaves gaps: what happens when externalMessageId or externalConversationId already exists, and whether sub-resources like subject or attachments are editable afterward via inboxAppUpdateMessage.

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 coverage is 100%, so the baseline would be 3, but the description adds a cross-parameter rule not present in the schema: conversations are keyed by YOUR externalConversationId, which explains how the caller's IDs relate to conversation identity. The first-message requirement for person/owner largely restates the schema's own field notes.

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 pairs a specific verb with a specific resource ('Add a message to an inbox app conversation') and adds a non-obvious scope fact: the conversation is auto-created on first use. It never names the closely related siblings (inboxAppUpdateMessage, inboxAppAddNote, inboxAppUpdateConversation), so differentiation is left to inference from the verb.

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?

It gives a real prerequisite — person and owner are required only on the first message of a conversation — which is useful when-to-use context. It stops short of routing guidance: nothing says when to use this instead of inboxAppUpdateMessage or inboxAppAddNote, which are the obvious adjacent tools.

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