Skip to main content
Glama

reddit_vote

Vote on a Reddit post or comment by setting an upvote, neutral, or downvote direction with the target ID.

Instructions

Vote on a Reddit post or comment.

Input Schema

NameRequiredDescriptionDefault
idYes
dirYes1=upvote, 0=neutral, -1=downvote
access_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.7/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. It does not disclose that this is a mutation requiring an access token, whether votes can be changed or removed, whether the operation is idempotent, or what the response contains. Only the basic scope (post or comment) is mentioned.

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 description is a single, front-loaded sentence with no wasted words. However, its extreme brevity contributes to the missing behavioral and parameter context, so it is efficient but arguably underspecified rather than optimally concise.

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 mutation tool with no annotations, no output schema, and only 33% parameter coverage, the description is too sparse. An agent lacks essential information about authentication, ID format, vote replacement behavior, and expected response.

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 only 33%, and the description adds no meaning beyond what the schema states. It does not explain the expected format of 'id' (e.g., fullname like t3_ or t1_) or what 'access_token' is for, leaving key parameter ambiguity unresolved.

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?

The description states a specific verb and resource: voting on a Reddit post or comment. It is clearly distinct from sibling tools like reddit_read, reddit_search, or reddit_post, though it does not explicitly name alternatives or clarify how it differs from other mutation tools.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites such as authentication requirements, and no explanation of when not to use it. The only usage signal is the implied scope of voting on posts or comments.

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