Reddit MCP Server

delete_comment

DestructiveIdempotent

Permanently remove a Reddit comment you authored by providing its ID. Irreversible deletion for comments; use delete_post for posts.

Instructions

Permanently delete one of your own comments. Mutating and destructive but idempotent — deleting an already-deleted comment is a no-op. Requires REDDIT_USERNAME and REDDIT_PASSWORD, and only works on comments authored by the authenticated account. Only affects the comment you name; use delete_post for posts. WARNING: this cannot be undone — the content is removed, though the comment id remains.

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": {
      "thing_id": "<thing_id>"
    },
    "name": "delete_comment"
  }
}

Input Schema

Name	Required	Description	Default
`thing_id`	Yes	The comment to delete: a full thing id 't1_<id>' or just the base36 comment id '<id>' (the 't1_' prefix is added automatically). Must be a comment you authored.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.3Aug 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The annotations already state destructive and idempotent, and the description reinforces that without requiring long original. It also adds critical beyond-annotation details: the required REDDIT_USERNAME and REDDIT_PASSWORD, the authorization/ownership limitation, and the subtle detail that the comment id persists after the content is removed. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is four tight sentences with no wasted words. It front-loading the most important facts, following with limitations, and closes with the risk warning. Each sentence serves a clear purpose.

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 single-parameter, no-output-schema deletion tool, the description covers all necessary areas: purpose, scope, auth, idempotency, permanence, and alternative. The annotations and sibling context complete the picture sufficiently, so the description is fully complete.

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?

The only parameter, thing id, is fully documented in the schema at 100% coverage, including the accepted format and automatic 't1_' prefix. The tool description adds no extra symbol-flavor meaning beyond that comprehensive schema, so baseline 3 is appropriate because the schema carries the load.

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 description opens with 'Permanently delete one of your own comments,' using a strong verb-resource pair and the scope. It further differentiates from the sibling delete simple by explicitly saying 'use delete_post for posts,' making its purpose distinct.

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?

The description gives clear when-to-use guidance for deleting a comment the authenticated account owns, when-not-to-use by excluding posts and comments authored by others, and names the alternative delete_post for posts. This covers the key decision boundary.

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