Skip to main content
Glama

Find Reddit threads or X conversations

reach_find

Start the run behind Assisted posts in the results app, for the platform the founder asked about. reddit: questions their buyers asked on Reddit this month, searched in the product's own communities first (the exact tool it plugs into, the buyer's exact job) with one broad sub beside them, a reply for each, plus a post of their own where a subreddit allows it, up to six drafts. x: posts from the last couple of days where their buyers talk about the problem the product solves, one reply each, up to five. Runs in the background, about two minutes; a run that finds nothing is not charged. Costs $2.20 for Reddit and $1.60 for X, charged only when it finds 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": {
      "platform": "<platform>"
    },
    "name": "reach_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Strong beyond what the annotations convey: asynchronous background run of about two minutes, no charge for empty runs, $2.20 Reddit / $1.60 X charged only on found drafts, explicit confirmation requirement, and 'Nothing is posted' which reinforces destructiveHint=false. Missing only what happens on failure or how the returned drafts link is later consumed.

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

Conciseness2/5

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

Everything is crammed into a single run-on block of semicolon-chained clauses, and the most important facts (cost, confirmation, nothing posted) trail at the end rather than being front-loaded. The dense marketing-inflected phrasing ('the exact tool it plugs into, the buyer's exact job') costs the reader more than it returns.

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 paid, asynchronous draft-generating tool with one parameter and no output schema, the definition covers cost, timing, charging policy, the confirmation gate, and the return value. The remaining gap is what the caller should do with the returned link next.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter and the schema coverage is 0%, but the description fully disambiguates the two enum values: reddit searches the product's own communities first with one broad sub alongside, x searches the last couple of days, with different draft caps for each. That is meaning the bare enum cannot supply.

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 definition does eventually convey what happens: it finds Reddit questions or X posts from the last couple of days and produces reply drafts (up to six for Reddit, five for X). But the opening sentence, 'Start the run behind Assisted posts in the results app,' is internal jargon that buries the verb, and the parenthetical '(the exact tool it plugs into, the buyer's exact job)' is close to unintelligible. Nothing distinguishes it from plausible siblings such as reach_drafts, drop_threads_find, or ideas_replies_find.

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?

It gives per-platform context ('the platform the founder asked about') and a clear pre-call gate: quote the price and wait for a yes. That is real guidance. It never says when to prefer this over a sibling like reach_drafts or ideas_replies_find, nor what to do if the founder declines, so selection between alternatives is left to inference.

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