Skip to main content
Glama

Buy discovery listing

buy_discovery_listing
Read-onlyIdempotent

Returns the paid x402 request for your order of Agent discovery listing (POST /buy/listing, $290 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/listing/check (email required there). If not delivered as described: full refund on request (/refunds). Submits your live paid x402 endpoint URLs to open discovery indexes within 48 hours of payment (acceptance is up to each index), then reports visibility on day 7; for domain alerts use buy_brandwatch; for contacts use buy_lead_list.

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": {
      "urls": "<urls>"
    },
    "name": "buy_discovery_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
emailNooptional: where to send the files too; without it they are on the order status page
contact_nameNooptional, for the generated files

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and non-destructive, and the description reinforces this with 'places and charges nothing' — consistent rather than contradictory. Beyond that it discloses pricing ($290), SLA (submission within 48 hours, acceptance up to each index, day-7 visibility report), and a refund path (/refunds), which an agent needs before invoking a paid flow.

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?

Key facts are front-loaded, but the body is a dense semicolon-and-parenthesis chain mixing pricing, payment mechanics, refund policy, fulfillment SLA, and sibling routing in one block. Every sentence carries information, yet the run-on structure makes the paid-vs-free distinction slower to parse than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the definition compensates by stating what comes back ('the order id and status link come back with the receipt') and how results are delivered (email or order status page). Combined with pricing, refund, and timing details, an agent has what it needs to call this correctly.

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?

Schema coverage is 67%, and the description adds real meaning beyond it: the URLs must be 'live paid x402 endpoint URLs', and email — optional in this schema — is 'required there' for the free check, a distinction the schema does not make. contact_name is never mentioned, leaving one gap.

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 definition names a concrete verb and resource ('Returns the paid x402 request for your order of Agent discovery listing') and immediately scopes it ('this call places and charges nothing'), which separates it from an actual purchase. It also names siblings (buy_brandwatch, buy_lead_list) as alternatives. It's slightly muddled because the fulfillment behavior ('Submits your live paid x402 endpoint URLs to open discovery indexes') describes the purchased service rather than this call, forcing the agent to reconcile two framings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing is provided: paid path 'Paying the request charges at once and skips the free check', and the optional free check is a separate call with email required. Alternatives for adjacent needs are named ('for domain alerts use buy_brandwatch; for contacts use buy_lead_list'), so the agent can select correctly without 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