Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

inboxAppUpdateMessage

Updates the delivery status of an inbox app message using its ID or externalMessageId; use it to track Sent, Delivered, Read, or Not Delivered without changing message text.

Instructions

Update the delivery status of an inbox app message. Identify the message by id or externalMessageId. Message text cannot be changed here.

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>"
    },
    "name": "inboxAppUpdateMessage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFUB ID of the inbox app message.
inboxAppIdYesID of the inbox app making the call.
deliveryStatusNoDelivery status.
externalMessageIdNoYour ID for the message; alone it identifies the message.
deliveryStatusErrorMessageNoUser-facing error text for Not Delivered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • 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 / externalMessageId
      Added value: +{
      +  "description": "Your ID for the message; alone it identifies the message.",
      +  "type": "string"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "FUB ID of the inbox app message.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / inboxAppId
      Added value: +{
      +  "description": "ID of the inbox app making the call.",
      +  "type": "string"
      +}
    • removedInput schema / properties / message
      Removed value: -{
      -  "description": "Updated message",
      -  "type": "string"
      -}
    • removedInput schema / properties / messageId
      Removed value: -{
      -  "description": "Message ID",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "messageId",
      -  "message"
      -]New value: +[
      +  "inboxAppId"
      +]
  2. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-readonly, non-destructive, non-idempotent, closed-world behavior, so the bar is lower. The description adds real context by bounding the mutation to delivery status only, but it says nothing about permissions, effects on other message fields, or what a successful call returns.

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 sentences, front-loaded with the action and scope, followed by identification guidance and a single clarifying exclusion. No filler or redundancy.

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 mutation with no output schema, the definition covers intent, lookup, and scope limits but omits what a successful update returns and how the required inboxAppId relates to the calling app. Adequate but with visible gaps for a mutation tool.

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 every parameter including the deliveryStatus enum and the error-message field is already documented. The description's only added value is clarifying that id or externalMessageId alone is sufficient for lookup, which the schema partially covers already; baseline 3 applies.

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 names a specific verb ('Update') and a narrowly scoped resource ('the delivery status of an inbox app message'), which separates it from siblings like inboxAppAddMessage or inboxAppUpdateConversation. It stops short of explicitly naming any sibling it replaces, so an agent must infer the boundary from names alone.

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?

'Message text cannot be changed here' is a useful exclusion that steers the agent away from expecting body edits, but it names no alternative tool for that case. There is no positive statement of when this tool should be preferred over other inbox-app mutations.

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