Skip to main content
Glama

ADS Beast

reddit_reply_draft

Drafts a reply to a Reddit thread and saves it as a task for a person to review and post. Nothing is posted. AI: 1 AI request.

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": {
      "thread_url": "<thread_url>",
      "brand_angle": "<brand_angle>"
    },
    "name": "reddit_reply_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idNo
thread_urlYesReddit thread URL.
brand_angleYesHow the brand should be mentioned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds important context beyond that: nothing is posted, the result is persisted as a task for human review, and it consumes one AI request (a cost/latency signal). It omits what happens on failure or whether duplicates are created, but the added value is genuine.

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?

Three short, front-loaded sentences with zero filler; the crucial 'Nothing is posted' clarification sits second, immediately after the action. The closing 'AI: 1 AI request.' is terse but readable as a cost hint, with only a slight loss of polish.

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

Completeness4/5

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

For a three-parameter drafting tool with no output schema, the description covers the essential outcome (a saved task, no publication) and the cost of invoking it. The main remaining gap is the undocumented client_id and the absence of any detail on what the saved task contains, but nothing blocks correct invocation.

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

Parameters3/5

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

Schema description coverage is 67%, so the schema already documents thread_url and brand_angle. The description adds no detail on any parameter, and client_id is undocumented in both places, leaving an agent to guess whether it scopes billing or brand context. Baseline 3 is appropriate given the schema does most of the work.

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 gives a specific verb and resource ('Drafts a reply to a Reddit thread'), and the follow-on clause makes clear the output is a reviewable task, not a live post. It does not explicitly name a sibling it differs from, so it falls short of a 5, but an agent can distinguish it from planning tools like reddit_amplification_plan from the text alone.

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?

Usage is implied rather than stated: drafting a reply to a specific thread URL for human review. The description does not say when to choose this over reddit_amplification_plan or reddit_opportunities, nor does it describe prerequisites such as owning the thread or needing client context. No exclusions or alternatives are offered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.