Subscribe to or unsubscribe from a Reddit subreddit by specifying the subreddit name and action, so you can manage your Reddit subscriptions directly from the agent workflow.
Subscribe to or unsubscribe from a Reddit subreddit.
| Name | Required | Description | Default |
|---|---|---|---|
| sr | No | Subreddit name alias | |
| action | Yes | sub or unsub | |
| subreddit | No | ||
| access_token | No |
Changes observed during successful MCP inspections.
v0.1.11Input schema / properties / sr / descriptionAdded value: +"Subreddit name alias"Input schema / properties / subredditAdded value: +{
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "access_token",
- "sr",
- "action"
-]New value: +[
+ "action"
+]v0.1.5Does 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 discloses that the tool can both add and remove a subscription, which is the key trait, but says nothing about authentication requirements, idempotency, or whether unsubscribing is reversible. For an account-mutating tool this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler and the resource stated immediately. It is efficient, though its brevity is part of why other dimensions are underspecified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With four parameters, no annotations, no output schema, and a duplicated subreddit concept in the schema, the description is too thin for an agent to call it confidently. It should clarify which identifier to use and note the auth requirement.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%: sr and action are documented, while subreddit and access_token are not. Critically, the description does not resolve the ambiguity of having two separate subreddit-identifying parameters (sr as an alias vs subreddit), which is exactly the kind of clarification prose should add beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb pair (subscribe/unsubscribe) and resource (Reddit subreddit), making it clearly distinct from siblings such as reddit_read, reddit_vote, and reddit_post. It is clear but does not explicitly contrast itself with any alternative tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 versus reddit_vote or reddit_read, no mention that it requires an authenticated user, and no statement about what happens on repeat calls. The only usage information is implied by the tool name and the enum.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.