Skip to main content
Glama

List Open Listings

list_open_listings
Read-only

Fan listings on XP open to offers, filterable by event, performer and whole-listing amount -- 'what's open near me this weekend?'. Listings the caller muted are left out. Each listing's identifier is what get_open_listing and buy_listing_now take; buy_listing_now buys a listing outright at its asking price. Event inventory at listed prices is in get_ticket_listings. Requires sign-in and the read:bids scope.

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

Input Schema

NameRequiredDescriptionDefault
daysNoOnly include offers created within this many days.
limitNoMax offers to return after fetch.
sort_byNoSort field: created_at, event_date, amount, state, updated_at.created_at
performerNoFilter by performer name substring.
event_nameNoFilter by event title substring.
max_amountNoDeprecated, use max_amount_usd. Micro-USDC (50_000_000 = $50.00).
min_amountNoDeprecated, use min_amount_usd. Micro-USDC (50_000_000 = $50.00).
sort_orderNoSort direction.desc
max_amount_usdNoMaximum total for the whole listing in dollars (all its tickets together), not per ticket.
min_amount_usdNoMinimum total for the whole listing in dollars (all its tickets together), not per ticket.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / sell_to_xp
      Removed value: -{
      -  "default": true,
      -  "description": "If true, only offers where sell_to_xp is true.",
      -  "type": "boolean"
      -}
  2. Changed4 schema fields changed
    • changedInput schema / properties / max_amount / description
      Previous value: -"Maximum listing amount in USDC 6-decimal raw units (50_000_000 = $50.00 USDC). Multiply dollars by 1_000_000."New value: +"Deprecated, use max_amount_usd. Micro-USDC (50_000_000 = $50.00)."
    • addedInput schema / properties / max_amount_usd
      Added value: +{
      +  "description": "Maximum total for the whole listing in dollars (all its tickets together), not per ticket.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / min_amount / description
      Previous value: -"Minimum listing amount in USDC 6-decimal raw units (50_000_000 = $50.00 USDC). Multiply dollars by 1_000_000."New value: +"Deprecated, use min_amount_usd. Micro-USDC (50_000_000 = $50.00)."
    • addedInput schema / properties / min_amount_usd
      Added value: +{
      +  "description": "Minimum total for the whole listing in dollars (all its tickets together), not per ticket.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the description adds real value beyond them: muted listings are silently excluded, sign-in plus the read:bids scope are required, and each listing's ID is the key consumed by get_open_listing and buy_listing_now. It does not mention pagination or the significance of the default 1-day window, which the schema covers.

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?

Front-loads what is listed and how it can be filtered, then follows with exclusion behavior, ID chaining, and auth. The aside explaining that buy_listing_now buys outright at asking price is slightly tangential to listing retrieval, but the whole definition stays tight and every other sentence carries operational weight.

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 an output schema, full annotation coverage, and 100% parameter documentation, the remaining burden is behavior and routing, both of which are handled (muted exclusion, auth scope, ID chaining, sibling for listed-price inventory). The only meaningful omission is any note about the default created-within-1-day window that shapes what 'open' actually returns.

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 description coverage is 100%, so the schema already documents every parameter including the deprecated micro-USDC amount fields and the whole-listing (not per-ticket) amount semantics. The description reinforces the whole-listing amount framing and the filter axes but adds no syntax or default-window guidance beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb and resource: fan listings open to offers, with the filter axes (event, performer, whole-listing amount) named up front. It explicitly contrasts with get_ticket_listings ('Event inventory at listed prices is in get_ticket_listings'), so an agent can separate the two without opening either schema.

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?

Gives a concrete usage scenario ('what's open near me this weekend?') and an explicit alternative for a different need (get_ticket_listings for event inventory at listed prices). It also tells the caller where to go next (get_open_listing, buy_listing_now) but does not address when to prefer this over list_my_listings or list_muted_listings.

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