Skip to main content
Glama

Find and write the replies about a feature that shipped

ideas_replies_find

Once a feature built from an idea is live: the run behind Assisted posts (the same as reach_find), aimed at this feature, for one platform. The idea's own posts still open for a reply go first, then Reddit's or X's search for people asking for it or stuck on the problem it solves now, ranked and checked the way reach runs are (X a week old at most; Reddit open threads, each subreddit's self-promotion rules). One reply each, written to that post and telling them it shipped, up to 5; never a thread with a draft or a recorded reply already. Runs in the background, about two minutes. Costs $1.40, charged only when it writes drafts: tell the founder the price and wait for a yes. Returns the link to the drafts. Nothing is posted.

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": {
      "key": "<key>",
      "platform": "<platform>"
    },
    "name": "ideas_replies_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe idea's key (IDEA:<slug>)
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already mark this as a non-read-only, open-world, non-destructive operation, and the description adds substantial context beyond them: background execution, ~2 minute runtime, a $1.40 cost charged only when drafts are actually written, a required confirmation step, and the side-effect boundary ('Nothing is posted', only drafts). It even discloses the ranking and verification rules applied to candidate posts. That is unusually complete behavioral disclosure for a mutation tool.

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?

The timing/scope clause is correctly front-loaded, and nearly every sentence carries operational information (cost, runtime, exclusions, return value). However, it is delivered as long run-on sentences with stacked parentheticals and internal shorthand ('the way reach runs are'), which costs readability and makes the cost/confirmation requirement easy to skim past.

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 costly, background, draft-writing tool with no output schema, the description covers what an agent most needs: preconditions, exclusions, price and confirmation, runtime, and the fact that a link to the drafts is returned. The main remaining gap is parameter-level guidance for `key` and `platform`, which the reader must infer from product context.

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 50% and the description only gestures at parameters through phrases like 'aimed at this feature' and 'for one platform'. The `key` parameter's IDEA:<slug> format and its meaning are left entirely to the schema, and the description adds no constraints on `platform` beyond what the enum already shows. Baseline 3 is warranted since the schema carries most of the load, but there is no compensating detail.

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 concrete verb-plus-resource: it finds replyable posts for a shipped feature and writes one reply each into drafts. It also positions itself against siblings, explicitly saying it is 'the run behind Assisted posts (the same as reach_find), aimed at this feature' and distinct from the idea's own posts. The phrasing is dense and jargon-heavy ('the run behind Assisted posts'), so an agent unfamiliar with the product's vocabulary needs a second read, which keeps it from a 5.

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?

Timing is stated unambiguously ('Once a feature built from an idea is live'), and there are explicit exclusions: 'never a thread with a draft or a recorded reply already'. It also states a gating condition before invocation: tell the founder the price and wait for a yes. It does not spell out what to use instead when the feature is not yet live, so the alternative routing is only implied.

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.

Resources