Skip to main content
Glama
Sign In

PostRite

by app.postrite.mcp
OverviewDiscussionsAdmin

Set comments' triage status

set_comment_status
Idempotent

Mark comments NEW, SEEN or DONE (resolved) in PostRite's inbox — what the team sees as pending. Changes nothing on the network. Up to 100 comments at once. 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

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": {
      "commentIds": "<commentIds>",
      "status": "<status>"
    },
    "name": "set_comment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesDONE resolves; NEW puts them back in the pending list
commentIdsYesComment IDs from list_comments
organizationIdNoOrganization 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

NameRequiredDescriptionDefault
updatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only give the generic safety profile (non-read-only, idempotent, non-destructive, open-world); the description goes well beyond them. It discloses the mutation's blast radius ('Changes nothing on the network'), the batch ceiling, the owner-only org setting prerequisite, the concrete failure signal (MCP_INBOX_DISABLED), and two distinct re-authorization/reconnection scenarios an agent or its user must resolve before retrying.

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-loads what it does and its non-network scope, then packs limits and prerequisites into a small number of dense sentences with no filler. The final sentence on reconnection is long and clause-heavy, but every clause covers a real failure path.

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?

With an output schema and full-coverage annotations already available, the description supplies exactly the missing operational context: prerequisites, permission/reconnect requirements, error code, and the batch limit. Nothing needed to invoke it correctly is absent.

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 three parameters are already documented, including the enum meaning for status and the organizationId conditional. The description's 'DONE (resolved)' and 'what the team sees as pending' restate rather than extend the schema, and the 100-item limit duplicates maxItems, so baseline 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 (mark) plus the resource (comments) and enumerates the exact target states NEW, SEEN, DONE, scoping them to PostRite's inbox. The clause 'what the team sees as pending' plus 'Changes nothing on the network' separates it from siblings like reply_to_comment, set_comment_hidden and delete_comment without needing to open their schemas.

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 situational context: it is the inbox triage operation, an internal state change only, capped at 100 comments, and gated on a specific org setting. It does not explicitly name alternatives (e.g. use set_comment_hidden to hide publicly, reply_to_comment to answer), so there is no when-not guidance, but the intended use is unambiguous.

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

All PostRite toolsInspect
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