PostRite

Delete a comment

delete_comment

DestructiveIdempotent

Delete a comment on the network, for everyone. Cannot be undone — prefer set_comment_hidden unless the comment is a scam, a malicious link or abuse. Also needs the organization's "Allow deleting via remote MCP" setting (else 403 "MCP delete is disabled"), and is refused with the reason when actions.canDelete is false. 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": {
      "commentId": "<commentId>"
    },
    "name": "delete_comment"
  }
}

Input Schema

Name	Required	Description	Default
`commentId`	Yes	Comment ID from list_comments
`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
`deleted`	No
`commentId`	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?

Beyond the destructiveHint/idempotentHint annotations, it discloses irreversibility, the precondition that actions.canDelete must be true, the specific 403 "MCP delete is disabled" response tied to the organization setting, the MCP_INBOX_DISABLED case, required comment/chat permissions, and the reconnect/re-registration steps. This is far more than the annotations carry.

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?

The critical scope and the set_comment_hidden routing are correctly front-loaded in the first two sentences. The trailing authorization paragraph is a long run-on that bundles two separate settings plus reconnect instructions, which makes it harder to scan, though every clause is factually 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 destructive, permission-gated mutation, the description covers failure modes, prerequisites, named alternatives, and recovery steps; the output schema handles return shape and the annotations handle the safety profile. Nothing an agent needs before calling 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 coverage is 100%, and the schema already explains commentId's origin and the conditional organizationId rule, so the description adds no parameter-level meaning. Baseline 3 applies when the schema does all the work.

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?

The first sentence gives a specific verb and resource ("Delete a comment") plus the crucial scope qualifier "on the network, for everyone," which separates it from the sibling set_comment_hidden. An agent can distinguish it from archive_post, delete_media, or set_comment_status 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?

It names the preferred alternative (set_comment_hidden) and the exact conditions that justify escalation to deletion: scam, malicious link, or abuse. That is an explicit when-and-when-not rule rather than implied usage.

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?