XP Tickets

List Open Listings

list_open_listings

Read-only

From XP's connected order book of resale listings. Use when a buyer wants to browse fan listings open to offers on XP (e.g. 'what's open near me this weekend', 'open listings with active offers'), then make an offer with make_offer_on_listing or buy one outright with buy_listing_now. Filterable by event, performer, and amount. Requires auth and read:bids scope. This is the offer/negotiation surface -- for a plain buy-now at the asking price without an offer, use search_events and get_ticket_listings instead.

Input Schema

Name	Required	Description	Default
`days`	No	Only include offers created within this many days.
`limit`	No	Max offers to return after fetch.
`sort_by`	No	Sort field: created_at, event_date, amount, state, updated_at.	created_at
`performer`	No	Filter by performer name substring.
`event_name`	No	Filter by event title substring.
`max_amount`	No	Deprecated, use max_amount_usd. Micro-USDC (50_000_000 = $50.00).
`min_amount`	No	Deprecated, use min_amount_usd. Micro-USDC (50_000_000 = $50.00).
`sort_order`	No	Sort direction.	desc
`max_amount_usd`	No	Maximum total for the whole listing in dollars (all its tickets together), not per ticket.
`min_amount_usd`	No	Minimum total for the whole listing in dollars (all its tickets together), not per ticket.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

removedInput schema / properties / sell_to_xp

Removed value: -{
-  "default": true,
-  "description": "If true, only offers where sell_to_xp is true.",
-  "type": "boolean"
-}

Changed4 schema fields changedOct 14, 2026

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"
+  ]
+}

First observedOct 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: auth plus the read:bids scope requirement, and the fact that results flow into an offer-negotiation workflow. It says nothing about result volume or truncation behavior, but the output schema covers the return shape.

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?

Purpose is front-loaded, then usage examples, downstream tools, filters, auth, and the negative routing — roughly the right order with no filler. It is dense (five clauses in one block) but every sentence carries information an agent needs.

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 10 optional parameters, full schema coverage, an output schema and read-only annotations, the description supplies what structure cannot: auth scope, workflow position, and sibling routing. The only gaps are edge behavior around limits and the deprecated amount fields, which are minor given the schema carries them.

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 100%, so all 10 parameters are documented structurally, which sets the baseline at 3. The description only restates the filterable dimensions at a high level ('event, performer, and amount') and adds no syntax or format detail. It also doesn't clarify the odd mismatch where the schema's `days` and `limit` descriptions talk about offers rather than listings, nor does it mention the deprecated min_amount/max_amount fields — though the schema itself flags both.

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+resource ('list resale listings from XP's connected order book') and immediately names the surface as the offer/negotiation one, distinguishing it from the buy-now siblings. An agent can tell this apart from get_ticket_listings or search_events without opening any schema.

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 gives concrete triggering examples ('what's open near me this weekend'), names both downstream actions (make_offer_on_listing, buy_listing_now), and explicitly states when NOT to use it: for a plain buy-now at asking price, use search_events and get_ticket_listings. That is a full when/when-not/alternatives statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XP Tickets tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?