PostRite

List comments

list_comments

Read-only

List comments people left on the organization's connected accounts (Instagram, Facebook, and Threads/TikTok where switched on), newest first, as the Comments inbox shows them. status NEW is what nobody has triaged; unanswered: true is what nobody has replied to. Each item carries actions (canReply/canHide/canDelete with the blocked reason when false) — read it before acting. A kind of MENTION_COMMENT/MENTION_CAPTION is the account mentioned on someone else's post: it can be replied to, never hidden or deleted. Call open_comments_inbox first in each run. 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_comments"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size, up to 50
`cursor`	No	nextCursor from the previous page
`hidden`	No	true = only hidden comments, false = only visible ones
`search`	No	Text the comment or its author contains
`status`	No	NEW (not triaged yet), SEEN, or DONE (resolved)
`platform`	No	Only comments on this network
`unanswered`	No	true = only comments nobody has replied to yet
`connectionId`	No	Only comments on 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
`comments`	No
`nextCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only/non-destructive safety, and the description adds real operational context on top: newest-first ordering, the owner-only "Let AI assistants answer comments and messages" setting, the specific MCP_INBOX_DISABLED error code returned when absent, and a reconnect/remove-and-re-add remedy for stale authorizations. It also discloses per-item capability flags with blocked reasons and the rule that mention-type comments can be replied to but never hidden or deleted.

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?

Front-loaded with purpose and scope, then prerequisites — a sensible order. It is a dense single block with mild redundancy against the schema on `status`/`unanswered`, and the client re-registration sentence is long, though the detail is genuinely operationally useful.

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

Completeness5/5

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

For a 9-parameter filtered list tool with an output schema, everything an agent needs is present: entry-point sequencing, authorization and org-setting prerequisites with the failure code, filter semantics, pagination via cursor/limit, and how to interpret the returned `actions` and `kind` fields before mutating anything.

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 baseline is 3. The description's gloss on `status` NEW and `unanswered` largely restates the schema's own wording ("not triaged yet", "nobody has replied to yet") rather than adding new meaning such as default sort interaction or how filters combine.

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 ("List comments") plus scope: connected accounts on Instagram, Facebook, Threads/TikTok, newest first, matching the Comments inbox view. The mention-kind nuance (MENTION_COMMENT/MENTION_CAPTION) further sharpens what is and isn't included, so an agent can separate it from get_comment_thread or list_conversations without opening schemas.

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

Usage Guidelines5/5

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

Explicitly routes sequencing ("Call open_comments_inbox first in each run") and disambiguates two easily-confused filters: `status` NEW for untriaged versus `unanswered: true` for unreplied. It also tells the agent to read `actions` before acting, which is a concrete precondition rather than vague advice.

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?