Skip to main content
Glama
Sign In

Reeling

by io.github.yomariano
OverviewDiscussionsAdmin

reeling_schedule_community_autopilot

Schedule 3 daily Reply-Only Reddit comments per day on autopilot (default 7 days = 21 replies: 1 Pure Karma + 2 Hidden Anti-Sell Mentions/day) across target subreddits and keywords.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reeling_schedule_community_autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to schedule (default: 7).
api_keyNoOptional Reeling API key.
keywordsNoTarget niche keywords to match daily threads.
project_idNoProject UUID to schedule daily autopilot replies for.
subredditsNoTarget subreddits (e.g. ['smallbusiness', 'entrepreneur', 'SaaS']).
project_nameNoProject or brand name (e.g. 'VoiceFleet.ai', 'Reeling.app', 'Unrust.dev').
replies_per_dayNoReplies per day (default: 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 usefully discloses the reply composition (1 Pure Karma + 2 Hidden Anti-Sell Mentions per day) and the derived volume (21 replies over 7 days), which is real behavioral detail. However it omits side effects of scheduling, whether the schedule can be cancelled, auth requirements, and what happens if keywords match nothing.

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?

A single dense, front-loaded sentence with no filler; the cadence and default math come first. It is slightly jargon-heavy ('Pure Karma', 'Hidden Anti-Sell Mentions') for an uninitiated agent, but nothing is wasted.

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

Completeness3/5

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

With 7 all-optional parameters, no annotations, and no output schema, the description needs to do more. It covers the core action and defaults but leaves the agent guessing about required inputs in practice (project_id or project_name?), authentication, and what the call returns.

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 coverage is 100%, so the baseline is 3. The description does add value by linking days × replies_per_day to a concrete output count and by explaining the 1+2 reply-type split, but it says nothing about the meaning or relationship of project_id vs project_name, or the optional api_key.

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?

Specific verb (Schedule) + resource (Reply-Only Reddit comments) + scope (target subreddits and keywords) + cadence. An agent can distinguish this from reeling_reply_to_comment (a one-off reply) or reeling_draft_community_answer (drafting only), though no sibling is named explicitly.

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?

The phrase 'on autopilot' implies this is the batch/scheduling path rather than the manual reply path, but the description never states when to prefer it over reeling_reply_to_comment or reeling_draft_community_answer, nor any preconditions (project must exist, keywords/subreddits must be supplied).

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