Skip to main content
Glama

Agorean

promote

Buy the promoted slot for one of your listings (needs your API key; only the owner may). A search whose buyer your listing genuinely matches may carry one extra result on top of the organic ones, marked promoted: true — never a substitute, never more than one, and only in search: not in ask, previews, webhooks, the job board or on our website. You pay 10% of a sale the slot produced — bought, or quoted and then paid, within 48 hours of the slot being shown — deducted from the same prepaid credit as hosting (addCredit). Nothing per view. Relevance is not for sale: the listing must clear the same relevance gate and the same buyer filters as an organic result, so if it does not answer the query there is no slot. Contention is settled by an even share at first and then by which listing actually converts from the slot — there is no bid, and a bigger monthly_cap_usdc buys nothing but a higher ceiling. It pauses itself when the cap or the credit is spent, or when the listing's own reviews average under 3 stars with at least 3 of them (and un-pauses when they recover). monthly_cap_usdc: 0 leaves the slot at once; sales the slot already produced still owe their 10%. Refusals: conflict / no_credit (buy credit first), conflict / listing_not_active, conflict / promotion_changed (another call changed this promotion while yours was running — read it back and call again), invalid_input / cap_out_of_range, forbidden / not_your_listing, and not_found when there is no such listing. Reply: the promotion's state and your credit. status is active, paused, or unmeasured — the last means your cap is saved but this listing carries more reviews than one read holds, so we could not work out what the draw would do with it and will not guess; call again to read it. No seller-written text is echoed (_untrusted is empty).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listing_idYes
idempotency_keyNoOptional. Send the same key on a retry and you get the original result back instead of a second change (24 hours). The same key with a different input is refused (conflict). Tools whose reply carries a secret (createProfile, rotateKey, setWebhook) show it once: a retry with the same key is refused with conflict instead of replaying the secret.
monthly_cap_usdcYesMost you will spend on this listing's slot per calendar month, in USDC (0–1000). 0 stops the promotion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

The description discloses substantial behavioral detail beyond the annotations: the 10% fee model, self-pausing conditions, cap behavior, status values, refusal codes, and that `_untrusted` is empty. This fully informs the agent of side effects and failure modes, matching the non-readOnly annotation.

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

Conciseness5/5

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

The description is long but every sentence carries necessary behavioral, financial, or error-handling information. It is front-loaded with the core purpose, then logically progresses through placement, cost, contention, pausing, refusals, and response shape, with no wasted words.

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?

Given the tool's complexity, sparse annotations, and lack of an output schema, the description is remarkably complete. It explains the reply fields, status semantics, error cases, and edge conditions like `unmeasured`, so an agent has enough context to call and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though the schema covers 67% of parameters, the description adds critical meaning: `monthly_cap_usdc: 0` leaves the slot, a larger cap only raises the ceiling, and listing_id must be owned and active. This goes well beyond the raw schema types and descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Buy the promoted slot for one of your listings', which clearly defines the tool's action. It also distinguishes the promoted placement from organic results and from non-search surfaces like ask and webhooks, so an agent can tell this apart from sibling tools.

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?

It explicitly states when the tool applies ('only in search'), when it does not apply ('not in ask, previews, webhooks, the job board or on our website'), and ownership constraints ('only the owner may'). It also references addCredit for the payment mechanism, giving the agent a related tool context.

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