Skip to main content
Glama
UserClimb

UserClimb

by thomaslrw

Get growth moves beyond posting

get_growth_moves
Read-only

Find user-growth tactics beyond content posting, including communities, outreach, creator partnerships, launches, app store, referrals, and offline ideas. Select a category to focus recommendations.

Instructions

Ways to get users beyond posting content: communities and conversations, direct outreach, creators and partnerships, launch and discovery, app store growth, referrals, and offline ideas.

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": "get_growth_moves"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional. One category only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond the category list — no indication of how many moves are returned, whether results are static or parameterized, or how the optional category narrows the response.

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 sentence with the scope front-loaded and no filler. It is efficient, though it spends its words enumerating categories the enum already encodes rather than explaining the return.

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?

A one-parameter read-only tool is low complexity, but with no output schema the description should explain what a call yields (a list of growth moves, presumably filtered by category). That gap keeps it at merely adequate.

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% and the enum is fully self-documenting, so baseline 3 applies. The description's category list loosely mirrors the enum values but adds no syntax, default-behavior, or 'one category only' detail beyond what the schema states.

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

Purpose3/5

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

The description says it covers 'ways to get users beyond posting content' and enumerates seven categories, which tells an agent this is a growth-tactics lookup rather than a content tool. However, it never states the verb or output shape — whether it returns a list of ideas, one per category, or a single recommendation — so the purpose is only inferred from the title and the enum.

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 guidance on when to call this versus the sibling tools (get_hooks, get_playbook, writing_method) that likely also return marketing advice. The optional category parameter implies a filtered vs unfiltered mode, but the description never explains that choice or when to omit the parameter.

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