PostRite

List message conversations

list_conversations

Read-only

List direct-message conversations across the connected accounts (Instagram, Messenger and other channels switched on), most recent first. Each carries the contact, unreadCount, lastMessagePreview and window: isOpen says whether a message can be sent now (a network accepts replies only for a while after the contact's last message — 24 hours on Instagram and Messenger), canPrivateReply whether the one private reply to a comment is still available. Needs the organization's "Let AI assistants answer comments and messages" setting (owner-only; without it the api answers MCP_INBOX_DISABLED) and a connection authorized with the comments/chat permissions — one authorized before they existed must reconnect, and a client that kept its own registration from before then must remove PostRite and add it again.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_conversations"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size, up to 50
`cursor`	No	nextCursor from the previous page
`search`	No	Text the contact's name or username contains
`status`	No	OPEN, SNOOZED or CLOSED
`channel`	No	Only this messaging channel
`unreadOnly`	No	true = only conversations with unread messages
`connectionId`	No	Only this account (list_platform_connections)
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.

Output Schema

Name	Required	Description	Default
`nextCursor`	No
`unreadTotal`	No
`conversations`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it explains the messaging window (isOpen = replies accepted only within 24 hours on Instagram/Messenger), canPrivateReply semantics, ordering, the specific MCP_INBOX_DISABLED failure when the org setting is off, and the reconnect/re-register requirement after permissions changed. That is exactly the operational context an agent cannot get from 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.

Conciseness4/5

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

Purpose and return-shape facts are front-loaded in the first two sentences, with prerequisites trailing. The final sentence about clients re-adding PostRite is dense and slightly run-on, but each sentence carries distinct, non-redundant information.

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, yet the description still explains the two nuanced return fields (window.isOpen, canPrivateReply), which is helpful rather than wasteful. Auth, org-setting and reconnect requirements are all covered; nothing essential for a correct call is missing.

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 the schema already documents limit, cursor, search, status, channel, unreadOnly, connectionId and organizationId. The description adds no filter semantics, so it sits at the baseline rather than contributing meaning 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 (list direct-message conversations) plus scope (all connected accounts/channels) and ordering (most recent first). It does not name a sibling to distinguish itself from, so an agent must infer that get_conversation_messages is the per-thread follow-up.

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?

Usage is implied — this is the entry point that returns conversations with a lastMessagePreview, from which you would drill into messages — but the description never says when to use it instead of get_conversation_messages, list_comments, or list_platform_connections. The prerequisites it does give are setup conditions, not selection guidance.

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

All PostRite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?