Skip to main content
Glama

List Tickets for Sale

create_listing
Destructive

Lists tickets the seller holds for sale on XP -- 'sell my two seats for Friday', 'list section 104 row C'. Buyers then make an offer on the listing, and the seller answers with accept_offer or reject_offer; the tickets transfer only after an offer is accepted. is_ada, is_obstructed_view and is_sro are required inputs with no default. confirm=false returns a preview of the section, row, seats and those three flags; confirm=true creates the listing. A new listing is reviewed before it goes live: listing_state in the result is live, in_review or not_accepted, and only a live listing is visible to buyers. Requires sign-in.

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": {
      "event_id": "<event_id>",
      "quantity": "<quantity>",
      "is_ada": "<is_ada>",
      "is_obstructed_view": "<is_obstructed_view>",
      "is_sro": "<is_sro>"
    },
    "name": "create_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
gaNoTrue for general admission with no seat numbers.
rowNoRow, e.g. C. Omit for general admission.
is_adaYesRequired. True if accessible (ADA) seating. Ask the seller; never assume.
is_sroYesRequired. True if standing room only. Ask the seller; never assume.
confirmNoFalse (default) previews. True creates the listing.
sectionNoSection name exactly as the venue prints it, e.g. 104.
event_idYesEvent identifier from search_market or search_events.
quantityYesHow many tickets are being listed together.
last_seatNoLast seat number, if seated.
first_seatNoFirst seat number, if seated.
ask_per_ticket_usdNoOptional asking price per ticket in dollars. Omit to invite offers with no anchor.
is_obstructed_viewYesRequired. True if the view is obstructed. Ask the seller; never assume.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / is_ada / default
      Removed value: -false
    • changedInput schema / properties / is_ada / description
      Previous value: -"True for accessible seating."New value: +"Required. True if accessible (ADA) seating. Ask the seller; never assume."
    • removedInput schema / properties / is_obstructed_view / default
      Removed value: -false
    • changedInput schema / properties / is_obstructed_view / description
      Previous value: -"True if the view is obstructed."New value: +"Required. True if the view is obstructed. Ask the seller; never assume."
    • removedInput schema / properties / is_sro / default
      Removed value: -false
    • changedInput schema / properties / is_sro / description
      Previous value: -"True for standing room only."New value: +"Required. True if standing room only. Ask the seller; never assume."
    • changedInput schema / required
      Previous value: -[
      -  "event_id",
      -  "quantity"
      -]New value: +[
      +  "event_id",
      +  "quantity",
      +  "is_ada",
      +  "is_obstructed_view",
      +  "is_sro"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the sign-in requirement, the preview-vs-create split, the post-creation review pipeline with concrete listing_state values (live/in_review/not_accepted), and the fact that tickets only transfer after an offer is accepted. This tells the agent what side effects to expect and why a created listing may not be visible yet.

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 the purpose with illustrative utterances, then layers flow, preview behavior, and the review pipeline in a logical order. The confirm=preview/create sentence duplicates the schema's own confirm description, which is minor redundancy in an otherwise tight paragraph.

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?

For a 12-parameter mutation with an output schema, the description covers auth, side effects, the offer handoff, and the listing lifecycle states an agent must interpret. Nothing needed to call or interpret this correctly is missing.

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 the schema already documents every parameter including confirm, ga, and the ADA/obstructed/SRO flags. The description reinforces that is_ada, is_obstructed_view and is_sro are required with no default and restates confirm's preview semantics, which is helpful emphasis but adds little new meaning.

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 ('Lists tickets the seller holds for sale on XP') and grounds it in two concrete utterances ('sell my two seats for Friday', 'list section 104 row C'), so the agent knows this is the supply-side listing action rather than a read of existing listings.

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 clear context: use when the seller wants to offer seats, then route buyers' responses to accept_offer or reject_offer, and use confirm=false to preview before creating. No explicit 'do not use when' clause or named alternative for reading listings, so it stops short of a 5.

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