Skip to main content
Glama

growth_plan

Read-only

Build a growth plan from candidate subreddits: identify the strongest subreddit, list cross-post targets, and retrieve the viral recipe with optimal posting times.

Instructions

Build a growth plan from candidate subreddits: pick the safest strong one, list cross-post targets, and return its viral recipe and best posting times. No credentials needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNoArchive lookback, e.g. 30d/60d30d
subredditsYesCandidate subreddits to plan across
time_filterNoPattern window for the recipe: week|month|yearmonth

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description adds value by detailing the output (viral recipe, posting times) and noting no credentials are needed. However, it adds no further behavioral traits beyond what annotations provide, earning a 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys the tool's purpose and key details with no wasted words.

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?

With a complete input schema and an output schema (not shown but present), the description adequately covers the tool's functionality. It mentions output specifics and the input of candidate subreddits, making it complete enough for an agent to understand usage.

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% and all parameters have descriptions. The description does not add additional meaning beyond what the schema already provides, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it builds a growth plan from candidate subreddits, including picking a safest strong one, listing cross-post targets, and returning a viral recipe and best posting times. It distinguishes itself from sibling tools like find_target_subreddits_tool by focusing on planning rather than discovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage after obtaining candidate subreddits, and mentions 'No credentials needed'. However, it does not explicitly state when not to use this tool or compare it to alternatives, though the context is fairly clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/latent-9/reddit-growth-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server