Skip to main content
Glama

Outbound list

outbound_targets

People to write one short email to, from this product's outbound list. The list is filled from the sources that fit its buyers, picked from its brief, never by the caller: people who said in public in the last two weeks that they have the problem this product solves, asked for a tool like it, or complained about a tool named in its place (X posts and Hacker News comments, never Reddit: its users stay pseudonymous, so reach answers there in the thread), for every product; and, when its buyers are makers, founders, startups or software teams, teams who launched in the last two weeks on Show HN or today on Product Hunt. Model calls keep only people who could buy (no vendors, marketers, agencies or bots; for launches, small new teams with something to sell, no known brands, no rivals). Everyone is judged once and stays on the list until written to, skipped, or two weeks old, so asking again is free while it has people. When the list is short, a search runs in the background (a few minutes): call again afterwards. For each: found (pain or launch), the post or launch and its words, why, an angle to open with, and the email they published (their own profile, a Show HN author's "about", the launch's own site) checked with a verifier, or an address found and verified (a work email from their name and the site on their profile; for a launch, the address its domain's mail server accepts, a person's own before hello@). Never a guessed address. Up to count people with an address, then up to 3 pain posts with none, to answer in their own thread. People written to (record_action, meta.type "outbound", meta.person, meta.email) or skipped never come back, and no address is offered twice. The 20 inbox drafts a day are counted here: draftsLeftToday says how many are left, and a batch is never bigger. sender is the address the drafts go from (mail_setup). Reading the list is free. A search costs Costs $2.20 from the balance, charged only when it returns. charged only when it adds someone with an address; it starts on its own when fewer than count are ready and none ran in the last 6 hours, or with fresh. A call with skip only records the skips, free.

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

Input Schema

NameRequiredDescriptionDefault
skipNoPeople the founder will not write to, by person ("x:<handle>", "hn:<user>", "ph:<slug>"). Never offered again.
countNoPeople with an address to hand back. Default 10
freshNoSearch for new people even when the list still has some or a search ran lately. Only when the founder asked for one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"People in a new batch. Default 10"New value: +"People with an address to hand back. Default 10"
    • changedInput schema / properties / fresh / description
      Previous value: -"Find a new batch even when the last one still has people in it"New value: +"Search for new people even when the list still has some or a search ran lately. Only when the founder asked for one"
    • removedInput schema / properties / source
      Removed value: -{
      -  "description": "For testing one source only. Leave it out: the sources that fit this product's buyers run together",
      -  "enum": [
      -    "pain",
      -    "launches"
      -  ],
      -  "type": "string"
      -}
  2. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"\"pain\" (default): people who posted the problem. \"launches\": teams who launched today on Product Hunt or Show HN"New value: +"For testing one source only. Leave it out: the sources that fit this product's buyers run together"
  3. Changed3 schema fields changed
    • changedInput schema / properties / fresh / description
      Previous value: -"Find a new batch even when last week's still has people in it"New value: +"Find a new batch even when the last one still has people in it"
    • changedInput schema / properties / skip / description
      Previous value: -"People the founder will not write to, by person (\"x:<handle>\", \"hn:<user>\"). Never offered again."New value: +"People the founder will not write to, by person (\"x:<handle>\", \"hn:<user>\", \"ph:<slug>\"). Never offered again."
    • addedInput schema / properties / source
      Added value: +{
      +  "description": "\"pain\" (default): people who posted the problem. \"launches\": teams who launched today on Product Hunt or Show HN",
      +  "enum": [
      +    "pain",
      +    "launches"
      +  ],
      +  "type": "string"
      +}
  4. Added

TDQS

A3.5/5.0
Behavior4/5

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

With readOnlyHint=false and openWorldHint=true, the annotations only signal that this is not a pure read; the description carries the rest and does so substantively: a $2.20 charge, the 20-drafts-per-day ceiling exposed as draftsLeftToday, people written to or skipped never returning, and no address being offered twice. The cost sentences are garbled ('A search costs Costs $2.20... charged only when it returns. charged only when it adds someone with an address'), which muddies whether the charge attaches to a search or to an added address — a meaningful ambiguity for a paid call, which keeps this below 5.

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?

The content is front-loaded with the resource definition, but the body is a dense run-on paragraph mixing sourcing rules, filtering heuristics, caching, pricing, and draft limits. Several clauses are broken or duplicated ('Costs $2.20', 'charged only when it returns. charged only when it adds someone with an address'), forcing the reader to re-parse the cost model. Much of the sourcing detail is background about how the list is built rather than something the caller must act on.

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, stateful tool with no output schema, the description covers what an agent most needs: the shape of each returned person (found, the post or launch and its words, why, an angle, and a verified email), the persistence rules, the draft ceiling, and the sender requirement via mail_setup. The gaps are clarity rather than coverage — the charge trigger and the relationship to sibling target lists remain fuzzy.

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%, so the schema already documents all three parameters and the baseline is 3. The description adds modestly beyond it: count is explained as up to count people with an address plus up to 3 pain posts without one, and fresh as forcing a search even when people remain. Those are useful clarifications but they restate rather than extend the schema's own wording.

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 opening sentence states the resource plainly: people to write one short email to, drawn from this product's outbound list. That is a specific resource with an implied retrieval action, and the rest of the description elaborates on sourcing. It never distinguishes itself from likely siblings such as followup_targets, outreach_targets, or launch_targets, so an agent cannot tell from this text alone why it should pick this list over those.

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 operational guidance: asking again is free while the list has people, call again after a background search, use skip to record refusals for free, and fresh only when the founder asked for one. What is missing is comparative guidance — no statement of when to use this versus followup_targets, outreach_targets, or launch_targets, which is exactly the choice an agent faces among these sibling lists.

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