Skip to main content
Glama

Buy paid placement for a directory listing (paid, x402)

listing_promote

PAID: promote a directory listing you own above free rows for the plan term; paying again extends. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: from $0.0667 USDC.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe listing to promote. It must already exist and be owned by the paying wallet -- create it free with POST /listings.
dryRunNoOptional. true: a dry run -- nothing is sent or changed, and the 200 answer (served:true, dryRun:true) says what this call would do with the rest of your body, or which fields are missing. A dry run is a paid call at this price. false or absent: the call runs.
durationNoWhich placement plan to buy; it sets both the placement window and the price. See GET /pricing or the service_card tool for the live table.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / dryRun
      Added value: +{
      +  "description": "Optional. true: a dry run -- nothing is sent or changed, and the 200 answer (served:true, dryRun:true) says what this call would do with the rest of your body, or which fields are missing. A dry run is a paid call at this price. false or absent: the call runs.",
      +  "type": "boolean"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "id",
      -  "duration"
      -]
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Against annotations that only declare it is not read-only, not destructive, and closed-world, the description adds the traits that actually matter: the call costs money, the exact price floor and settlement chains, the two-step unpaid-then-paid protocol, and that repurchasing extends rather than duplicates. It also warns that a dry run is still billed, which is the kind of cost trap an agent would otherwise fall into.

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

Conciseness4/5

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

The 'PAID:' prefix front-loads the single most decision-relevant fact, and the payment loop is compressed into one sentence without waste. The trailing feedback and pricing sentences are borderline boilerplate, but the pricing note earns its place for a paid tool while the feedback channel is marginal.

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 semantics and does it well: unpaid calls return a price, paid calls promote or extend, and dry runs report what would happen. The remaining gap is the shape of a successful paid response and whether placement is per-category or global, but nothing needed to invoke the tool correctly is absent.

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 100%, so the baseline is 3, but the description adds meaning the schema does not carry: the duration choice is framed as a 'plan term' that evidently stacks across repeat purchases, and the non-schema _meta['x402/payment'] channel is explained. The id and dryRun parameters are left entirely to their schema descriptions, which is acceptable given how detailed those are.

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 opens with a specific verb and resource ('promote a directory listing you own above free rows') plus the scope ('for the plan term'), which is far more informative than the title alone. It stops short of naming the closest sibling (placement_order) or stating what makes this different from it, so an agent still has to infer the boundary from the resource noun rather than from explicit routing.

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 gives a clear usage workflow: call unpaid to get the price, then pay via _meta['x402/payment'] and call again, and it notes that paying again extends an existing placement. The ownership precondition is also stated. What is missing is any exclusion rule, e.g. when to prefer placement_order or what to do for a listing you do not own.

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