Skip to main content
Glama

Get Inbox Conversation

get_inbox_conversation
Read-onlyIdempotent

Get one direct message conversation with its messages, to read the thread before answering. 404 inbox_item_not_found when the id is unknown in this workspace. Needs the inbox.read permission, which every role holds.

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": {
      "id": "<id>"
    },
    "name": "get_inbox_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe conversation id, from list_inbox_conversations
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with conversation and messages: one { id, isOwn, text, hasAttachments, createdAt } per message. An InboxConversation: id, accountId, platform, accountName, participant { id, name, username, avatarUrl }, lastMessageText, lastMessageAt, lastMessageIsOwn, status, repliedAt, replyWindowEndsAt (the end of the 24-hour Facebook and Instagram reply window, else null), maxMessageLength and capabilities { canReply }.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "conversation": {
      +    "anyOf": [
      +      {
      +        "additionalProperties": true,
      +        "properties": {
      +          "accountId": {
      +            "description": "The account `id` from GET /social-accounts",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "accountName": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "capabilities": {
      +            "anyOf": [
      +              {
      +                "additionalProperties": true,
      +                "properties": {
      +                  "canReply": {
      +                    "type": [
      +                      "boolean",
      +                      "null"
      +                    ]
      +                  }
      +                },
      +                "type": "object"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "id": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "lastMessageAt": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "lastMessageIsOwn": {
      +            "type": [
      +              "boolean",
      +              "null"
      +            ]
      +          },
      +          "lastMessageText": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "maxMessageLength": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "participant": {
      +            "anyOf": [
      +              {
      +                "additionalProperties": true,
      +                "properties": {
      +                  "avatarUrl": {
      +                    "type": [
      +                      "string",
      +                      "null"
      +                    ]
      +                  },
      +                  "id": {
      +                    "description": "The platform user id",
      +                    "type": [
      +                      "string",
      +                      "null"
      +                    ]
      +                  },
      +                  "name": {
      +                    "type": [
      +                      "string",
      +                      "null"
      +                    ]
      +                  },
      +                  "username": {
      +                    "type": [
      +                      "string",
      +                      "null"
      +                    ]
      +                  }
      +                },
      +                "type": "object"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "platform": {
      +            "description": "One of: FACEBOOK, INSTAGRAM, THREADS, TIKTOK, TWITTER, BLUESKY, LINKEDIN, PINTEREST, YOUTUBE, MASTODON, TELEGRAM, GOOGLE_BUSINESS, TUMBLR, WORDPRESS",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "repliedAt": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "replyWindowEndsAt": {
      +            "description": "When the FACEBOOK and INSTAGRAM 24-hour reply window closes; null on other platforms",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "status": {
      +            "description": "One of: UNREAD, READ, DONE",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "messages": {
      +    "anyOf": [
      +      {
      +        "items": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "createdAt": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "hasAttachments": {
      +              "type": [
      +                "boolean",
      +                "null"
      +              ]
      +            },
      +            "id": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "isOwn": {
      +              "type": [
      +                "boolean",
      +                "null"
      +              ]
      +            },
      +            "text": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ],
      +    "description": "Oldest first"
      +  }
      +}
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description still adds real value with the specific 404 error code, the inbox.read permission requirement, and the note that every role holds it — details an agent cannot get from the structured fields.

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 front-loaded sentences, each earning its place: what it returns, the failure mode, and the auth requirement. No filler or redundancy.

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

Completeness4/5

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

An output schema exists, so return shape need not be described, and the description covers failure mode and permissions well. It does not address whether the embedded messages list is paginated, which is the only notable gap for a thread-reading 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%, and the schema already explains both id provenance and workspaceId semantics in detail, so a baseline 3 is appropriate. The description adds no parameter-level meaning beyond what the schema provides.

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?

States a specific verb and resource — 'Get one direct message conversation with its messages' — and adds scope ('one', 'with its messages') that separates it from the list_inbox_conversations sibling. The purpose ('read the thread before answering') is concrete and unambiguous.

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

Usage Guidelines4/5

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

Gives clear usage context with 'to read the thread before answering' and notes the 404 inbox_item_not_found case for an unknown id in the workspace. It stops short of explicitly naming alternatives such as list_inbox_conversations, but the 'one conversation' framing implies the choice well.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources