Skip to main content
Glama
Sign In
threadr-mcp

threadr-mcp

by msaeedsakib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edit_comment

Update your own Reddit comment by providing its comment ID and new content; authenticated users only.

Instructions

Edit 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>",
      "content": "<content>"
    },
    "name": "edit_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
comment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/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 behavioral burden. It usefully discloses that only your own comments can be edited and that authentication is required, but says nothing about whether edits are destructive/replace content, whether they are reversible, or any rate or permission limits.

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 compact sentence with the verb-resource pair front-loaded and the auth caveat appended; nothing is wasted. It is efficient, though its brevity borders on under-specification rather than tightness.

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

Completeness2/5

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

This is a destructive-shaped mutation with no annotations, no output schema, and 0% parameter coverage, yet the description supplies only two facts. Critical details for calling it correctly — whether the edit is full replacement, error behavior on foreign comments, and what the response returns — are absent.

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?

Schema description coverage is 0% and the description mentions neither parameter. The agent gets no explanation of what 'content' replaces, whether comment_id accepts a bare ID or a prefixed identifier, or the 10000-char limit semantics beyond the schema constraint.

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?

Names a specific verb ('Edit') and resource ('comment') and adds the ownership scope ('your own'), which distinguishes it from edit_post and delete_comment. It does not explicitly name or route to a sibling, so it falls short of a 5.

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

Usage Guidelines3/5

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

The parenthetical '(requires user auth)' signals a precondition, which is useful context for selecting this tool over read-only siblings. However, there is no guidance on when this is the right call versus edit_post, delete_comment, or reply_to_comment, so usage is only implied.

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