Skip to main content
Glama
Sign In
threadr-mcp

threadr-mcp

by msaeedsakib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_comment

Deletes one of your own Reddit comments using its comment ID; user authentication is required to confirm ownership.

Instructions

Delete your own comment (requires user auth)

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

Input Schema

NameRequiredDescriptionDefault
comment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that user auth is required and that only the caller's own comments can be deleted, which is meaningful behavioral context. It omits irreversibility, behavior when the comment isn't yours, and cascade effects on replies.

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?

A single short sentence with the core action front-loaded and the auth caveat in parentheses. Efficient, though the parenthetical could be tightened or better integrated.

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

Completeness3/5

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

For a simple single-parameter delete tool with no output schema, the description covers purpose, ownership, and auth, which is close to sufficient. However it leaves the parameter undocumented and doesn't clarify destructive/loss semantics, which matters most for a delete operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

One parameter with 0% schema description coverage, and the description says nothing about comment_id's format or where to obtain it. Since the schema provides no documentation and the description does not compensate, this is a clear gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Delete ... comment') and adds an ownership scope ('your own'), which distinguishes it from delete_post at a glance. It does not explicitly name siblings, but the resource noun is unambiguous.

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

Usage Guidelines2/5

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

No indication of when to use this versus edit_comment or delete_post, and no prerequisites or failure conditions are described. Only the implicit 'your own' constraint hints at usage boundaries.

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

Deploy Server

Other Tools