Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

inboxAppAddNote

Add an internal note to an inbox app conversation using your externalConversationId so teams can record context and follow-up details on the thread.

Instructions

Add an internal note to an inbox app conversation, keyed by your externalConversationId.

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>",
      "body": "<body>",
      "user": "<user>"
    },
    "name": "inboxAppAddNote"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesPlain-text body of the note.
userYesUser adding the note. Set id OR name/email.
inboxAppIdYesID of the inbox app making the call.
externalConversationIdYesYour ID of the conversation to add the note to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.0
    • addedInput schema / properties / body
      Added value: +{
      +  "description": "Plain-text body of the note.",
      +  "type": "string"
      +}
    • removedInput schema / properties / conversationId
      Removed value: -{
      -  "description": "Conversation ID",
      -  "type": "string"
      -}
    • addedInput schema / properties / externalConversationId
      Added value: +{
      +  "description": "Your ID of the conversation to add the note to.",
      +  "type": "string"
      +}
    • addedInput schema / properties / inboxAppId
      Added value: +{
      +  "description": "ID of the inbox app making the call.",
      +  "type": "string"
      +}
    • removedInput schema / properties / note
      Removed value: -{
      -  "description": "Note content",
      -  "type": "string"
      -}
    • addedInput schema / properties / user
      Added value: +{
      +  "description": "User adding the note. Set id OR name/email.",
      +  "properties": {
      +    "email": {
      +      "description": "User email if no ID.",
      +      "type": "string"
      +    },
      +    "id": {
      +      "description": "User ID adding the note.",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "User name if no ID.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "conversationId",
      -  "note"
      -]New value: +[
      +  "inboxAppId",
      +  "externalConversationId",
      +  "body",
      +  "user"
      +]
  2. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation. The description adds useful context that the note is 'internal' and that the conversation is addressed by the caller's own externalConversationId, but says nothing about duplicate-note behavior, note visibility to end customers, or permission requirements.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity is part of why usage guidance and behavioral detail are thin.

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?

Adequate for a simple four-parameter mutation whose schema and annotations are fully populated. Gaps remain around what an internal note means for visibility and what happens if the note is added repeatedly, which an agent cannot infer from structured fields alone.

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 all four parameters are already documented, including the id-or-name/email rule for the user object. The description's mention of externalConversationId reinforces 'your ID' but adds no format or constraint detail beyond the schema.

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?

States a specific verb and resource: 'Add an internal note to an inbox app conversation.' The qualifier 'internal note' implicitly separates it from the sibling inboxAppAddMessage, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. An agent choosing between inboxAppAddNote, inboxAppAddMessage, and createNote gets no stated rule for which to pick, and no prerequisites are mentioned.

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