PostRite

Open the comments inbox

open_comments_inbox

Idempotent

Open the comments inbox, the way a person opening it in the app does. Call this once at the start of every run, before list_comments. PostRite only receives comments for an organization someone reads: the first open turns ingestion on and imports the last 30 days, and ingestion stops after 30 days without an open. An empty list_comments right after the first open can mean the import is still running — queued says how many accounts are importing, and retryAfterSeconds when an open was throttled (it still counts). 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": "open_comments_inbox"
  }
}

Input Schema

Name	Required	Description	Default
`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
`queued`	No
`activated`	No
`retryAfterSeconds`	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 only say it is a non-read-only, idempotent, open-world, non-destructive call; the description goes well beyond that by disclosing the side effect (ingestion on, 30-day import, ingestion lapses after 30 days without an open) and the throttling behavior with 'queued'/'retryAfterSeconds'. It also spells out the two hard prerequisites — the owner-only organization setting whose absence returns MCP_INBOX_DISABLED, and a connection authorized with comments/chat permissions, including the reconnect/remove-and-re-add recovery path for stale registrations. No statement conflicts with readOnlyHint=false or idempotentHint=true.

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 the action and the invocation rule, then the mechanism, then the error paths — a sensible ordering with no filler sentences. It is dense and slightly run-on in the final sentence (permissions plus two separate recovery procedures stacked together), which costs a point but not readability.

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?

An output schema exists, so return values need no explanation, yet the description still supplies the interpretation the schema cannot: what 'queued' and 'retryAfterSeconds' mean and that a throttled open still counts. Combined with the auth and configuration prerequisites, an agent has everything needed to call this correctly on first attempt.

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 single organizationId parameter is already fully documented there, including the multi-org-required vs single-org-omitted rule. The description adds no additional meaning about the parameter, so the baseline of 3 applies.

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 ('Open the comments inbox') and immediately disambiguates it from the nearest sibling ('before list_comments'), even framing the mental model as 'the way a person opening it in the app does'. An agent can distinguish it from list_comments, get_comment_thread, and list_conversations without opening any schema.

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?

Gives an explicit invocation rule — 'Call this once at the start of every run, before list_comments' — plus the consequence of not calling it (no ingestion, no new comments received). It also explains what to do with a suspicious result (empty list right after first open may mean import still running) rather than leaving the agent to interpret ambiguity unaided.

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?