Skip to main content
Glama

reddit_comment

Posts a comment to Reddit by submitting text with a target parent ID and access token, enabling replies to posts or comments.

Instructions

Post a comment on Reddit.

Input Schema

NameRequiredDescriptionDefault
textYes
parent_idYes
access_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.11
    • changedInput schema / required
      Previous value: -[
      -  "access_token",
      -  "parent_id",
      -  "text"
      -]New value: +[
      +  "parent_id",
      +  "text"
      +]
  2. Addedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and fails to state that this is a mutating write operation, that authentication (the access_token parameter) is required, or any rate-limit/reversibility context. It only weakly implies a write via the word 'post'.

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

Conciseness3/5

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

A single front-loaded sentence with no filler, but it is under-specified rather than efficient; there is no wasted text, yet it lacks the content a write tool needs.

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?

For a three-parameter mutation tool with no annotations, no output schema, and no parameter documentation, the description omits too much: auth requirements, the parent_id format, and what is returned. An agent could not reliably call this without guessing.

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%, so all three parameters (text, parent_id, access_token) are undocumented structured fields. The phrase 'comment on Reddit' hints that parent_id identifies the target of the comment, but the critical fullname format (t1_/t3_ prefixes) and the role of access_token are never explained.

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?

"Post a comment on Reddit" names a specific verb (post) and resource (comment), so the agent knows exactly what action results. It does not differentiate from the closely related siblings reddit_post, reddit_thread, or comment_on, leaving the boundary between creating a comment versus creating a submission ambiguous.

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?

The description provides no when-to-use guidance and names no alternatives, even though the sibling list contains reddit_post and comment_on that an agent could easily confuse it with. Usage is only implied by the verb 'post'.

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