Skip to main content
Glama

Buy lead list

buy_lead_list
Read-onlyIdempotent

Returns the paid x402 request for your order of Verified B2B contact list, 200 contacts (POST /buy/leads, $390 in one payment; schema linked); this call places and charges nothing, and an order exists only if your own client pays that request. POST that JSON body to the URL with an x402 or MPP client; the order id and status link come back with the receipt. Bad input is refused before any charge. Paying the request charges at once and skips the free check; the free check is a separate, optional call: POST the same body plus your email to /buy/leads/check (email required there). If not delivered as described: full refund on request (/refunds). 200 contacts, delivered within 3 days of payment (up to 2 more days if the list is short); for domain alerts use buy_brandwatch.

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": {
      "profile": "<profile>",
      "keywords": "<keywords>"
    },
    "name": "buy_lead_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNooptional: where to send the files too; without it they are on the order status page
profileYeswho your customers are
regionsNodefault Any
keywordsYes
countriesNooptional ISO codes, e.g. DE
exclude_domainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • addedInput schema / properties / countries
      Added value: +{
      +  "description": "optional ISO codes, e.g. DE",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 5,
      +  "type": "array"
      +}
  4. Added

TDQS

A4/5.0
Behavior5/5

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

It goes well beyond the annotations by resolving the tension between the 'Buy' name and readOnlyHint: this call charges nothing, and an order exists only if the caller's own client settles the 402. It adds that bad input is refused before any charge, that payment is immediate and skips the free check, that refunds are available at /refunds, and that delivery takes three days plus up to two more. These are precisely the operational facts an agent needs before a money-adjacent action.

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?

All content is relevant, but the description is a long run-on chain of semicolons and parentheses that mixes payment mechanics, refunds, delivery SLA, and alternative routing. It is front-loaded in a single sprawling sentence rather than split into scannable statements, which costs readability despite zero filler.

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?

With no output schema, the description carries the return burden and does say the order id and status link come back with the receipt. It also covers price, delivery SLA, refunds, and the free-check alternative. The only substantive gap is enrichment of the non-email parameters.

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 67%, so the baseline is 3. The description adds meaning only for email, clarifying that it is required at /buy/leads/check even though it is optional in this tool's schema, and it says nothing about profile, keywords, regions, countries, or exclude_domains. The remaining parameters are documented only by the schema.

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 first sentence names a specific verb and resource: it returns the paid x402 payment request for a 200-contact B2B list at a fixed $390 price on POST /buy/leads. It also distinguishes itself from the free-check path and names buy_brandwatch for domain alerts. The unusually dense framing and the nested parentheticals make the core action slightly harder to grasp than the specificity deserves.

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?

It explicitly routes the agent: use the free check endpoint (/buy/leads/check, email required) for validation, and this call for the paid request, while noting that paying skips the free check. It also defers a different use case to buy_brandwatch. There is no blanket statement of when not to use it, but the alternatives and their conditions are stated.

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