Skip to main content
Glama

Get My Listing Status

get_my_listing_status
Read-only

One of the caller's own listings on XP, seen as the seller -- 'any new offers on my tickets?'. Returns the state, seats, disclosures, visible_to_buyers and the open offers on it, with amounts in dollars (amount_usd). visible_to_buyers, not the state, says whether buyers can see the listing. When is_seller is true, each open offer carries actions for accept_offer and reject_offer. When the listing has sold and awaits the seller's transfer, the result carries the transfer instructions and the remaining obligation. identifier comes from create_listing, list_my_listings or list_open_listings. Requires sign-in and the read:bids scope.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_my_listing_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesPublic listing identifier from create_listing (listing_identifier), list_open_listings or list_my_listings.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / identifier / description
      Previous value: -"Public listing identifier from list_open_listings or list_my_listings."New value: +"Public listing identifier from create_listing (listing_identifier), list_open_listings or list_my_listings."
  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 readOnly/openWorld annotations: discloses that amounts are in dollars (amount_usd), that visible_to_buyers rather than state governs buyer visibility, that is_seller=true attaches accept_offer/reject_offer actions, and that post-sale listings carry transfer instructions and remaining obligations. It also states the auth requirement and required scope (read:bids), which annotations do not cover.

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 seller perspective and the motivating question, then layers in semantics and prerequisites. It is dense and mostly earns its length, though the visible_to_buyers caveat is stated twice in slightly different 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?

For a single-parameter read tool with an output schema, the description covers everything an agent needs: what it returns, how to interpret the key fields, conditional payloads, and auth/scope requirements. No meaningful gap remains for correct invocation.

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% and the single parameter is fully described, so the baseline applies. The description's note about identifier provenance largely restates what the schema already documents, adding no new format or constraint detail.

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: fetches one of the caller's own listings 'seen as the seller', with a concrete user-intent paraphrase ('any new offers on my tickets?'). That framing cleanly separates it from buyer-facing siblings like get_open_listing or check_listing.

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?

Clearly scopes usage to the caller's own listings and states where the identifier comes from (create_listing, list_my_listings, list_open_listings), which effectively routes the agent away from public-listing tools. It does not explicitly name an alternative or a when-not condition, so it stops short of full routing guidance.

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