Skip to main content
Glama
Sign In

Reeling

by io.github.yomariano
OverviewDiscussionsAdmin

reeling_draft_community_answer

Draft a value-first, humanized community reply for X, Reddit (100% Reply-Only), or Quora using Stealth Anti-Sell Mention, Smart Mix, or 100% Pure Karma Help.

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": {
      "platform": "<platform>",
      "question_title": "<question_title>"
    },
    "name": "reeling_draft_community_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoOptional Reeling API key.
platformYesTarget platform ('x', 'reddit', or 'quora').
subredditNoOptional subreddit name if platform is 'reddit'.
project_idNoOptional project UUID.
reply_styleNoReply mode: 'stealth_anti_sell' (85% help + hidden middle mention), 'smart_mix' (60% stealth / 40% pure help), or 'pure_karma' (100% pure help).
question_titleYesTitle of the X post, Reddit thread, or Quora question.
project_contextNoOptional project name and background context.
question_snippetNoOptional body snippet or context of the question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / platform / description
      Previous value: -"Target platform ('reddit' or 'quora')."New value: +"Target platform ('x', 'reddit', or 'quora')."
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "reddit",
-  "quora"
-]New value: +[
+  "x",
+  "reddit",
+  "quora"
+]
    • changedInput schema / properties / project_context / description
      Previous value: -"Optional domain expertise or background context."New value: +"Optional project name and background context."
    • addedInput schema / properties / project_id
      Added value: +{
+  "description": "Optional project UUID.",
+  "type": "string"
+}
    • changedInput schema / properties / question_title / description
      Previous value: -"Title of the Reddit thread or Quora question."New value: +"Title of the X post, Reddit thread, or Quora question."
    • addedInput schema / properties / reply_style
      Added value: +{
+  "description": "Reply mode: 'stealth_anti_sell' (85% help + hidden middle mention), 'smart_mix' (60% stealth / 40% pure help), or 'pure_karma' (100% pure help).",
+  "enum": [
+    "stealth_anti_sell",
+    "smart_mix",
+    "pure_karma"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description bears the full burden, and it discloses very little beyond marketing framing. It never states whether the result is returned as text only or posted, whether an api_key/credit is required, or whether Reddit being "100% Reply-Only" is an enforced constraint.

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?

It is a single sentence with no filler clauses, which is the right size. However, it is front-loaded with stacked jargon ("value-first, humanized", "Stealth Anti-Sell Mention", "100% Pure Karma Help") that delays the routing-relevant information.

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 an 8-parameter generative tool with no output schema and no annotations, the description leaves key questions unanswered: what the returned draft looks like, whether it is persisted, and how it relates to the publish/reply siblings. The fully documented schema offsets some but not all of this.

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 100%, so the schema already defines every parameter and enum value, giving a baseline of 3. The description only echoes the platform and mode names, adding no format hints or interaction guidance (e.g., that subreddit matters only for Reddit).

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 names a specific verb ("Draft") and resource ("community reply") and enumerates the supported platforms and reply modes, so the agent knows what the tool produces. It does not differentiate from close siblings like reeling_reply_to_comment or reeling_adapt_content_ai, leaving overlap unresolved.

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 statement of when to choose this over reeling_reply_to_comment, reeling_humanize_content, or reeling_adapt_content_ai, and no preconditions or exclusions. The agent must infer from the word "Draft" that this does not publish.

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

All Reeling toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources