Skip to main content
Glama

Find drop threads and write a reply to each

drop_threads_find

Threads and posts that invite founders to share what they built ("drop your startup below", "what are you building", "let's get 10 people to try your app"), for one platform: reddit, open threads from the last two weeks in the communities where makers share and across Reddit, busiest and freshest first; x, posts from the last three days. Only posts that themselves ask for products are kept, so the reply names the product as the founder's own, with its address, and answers each thing the post asks; what a post asks in return (trying another builder's app) is in the draft's why, for the founder to do themselves. One reply each, up to 5; never a thread with a draft or a recorded reply already, never the founder's own post. The same run as reach_find, on Assisted posts, marked Drop thread. 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": {
      "platform": "<platform>"
    },
    "name": "drop_threads_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only say it isn't read-only; the description adds the expensive details an agent needs: it runs in the background for about two minutes, costs $1.40 charged only when drafts are actually written, caps at one reply per thread and five total, and never posts anything. It also discloses the de-duplication rules that determine which threads come back.

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?

Nearly everything earns its place, but it is delivered as one sprawling sentence with embedded parentheticals and clauses like 'with its address, and answers each thing the post asks', which makes the key facts (cost, background run, no posting) hard to locate. Front-loading the action and splitting the constraints and the billing rule into separate lines would improve scanability without losing content.

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, it covers timing, pricing and consent, dedupe rules, reply limits, and the return value ('the link to the drafts'). The notable omission is any precondition about the platform account being connected or what happens if reddit/x access is missing.

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?

The schema documents the single platform enum with 0% description coverage, so the description has to carry the meaning, and it does: reddit returns threads from the last two weeks from maker communities and across Reddit ordered busiest/freshest first, while x returns posts from the last three days. That is a clear value-to-behavior mapping, though it doesn't say whether reddit's community set is configurable.

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 specific resource (threads/posts inviting founders to "drop your startup") and a specific action (keep them and write one reply each), scoped to reddit and x with distinct windows. The title's "Find" undersells that it also writes drafts, but the body makes the combined find-and-draft behavior explicit and ties it to reach_find and the 'Drop thread' marking.

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 real operating guidance: pick a platform, tell the founder the $1.40 price and wait for a yes, and skip threads with an existing draft, a recorded reply, or the founder's own post. What it does not do is state when to call this instead of reach_find or ideas_replies_find; 'the same run as reach_find, on Assisted posts' hints at a relationship but leaves the selection rule implicit.

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