Skip to main content
Glama

List My Listings

list_my_listings
Read-only

The caller's own listings on XP, grouped by lifecycle category (active, pending, has_open_bids, awaiting_seller_transfer_proof and more) -- 'show the tickets I'm selling'. Paged per category: each category returns one page with its own pagination totals, has_more marks a further page, and offset pages on or state_category narrows to one category. 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_my_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoListings per state category, 1-200. Defaults to 25.
offsetNoSkip this many within each category. Use with limit to page.
state_categoryNoOptional: active, pending, has_open_bids, awaiting_seller_transfer_proof, needs_user_attention, ready_to_claim, rejected_bids, terminal.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), but the description adds genuinely new behavior: it requires sign-in and the read:bids scope, and it discloses the unusual per-category pagination model where each category has its own totals and has_more flag. It stops short of describing ordering or result-size limits, so it is not exhaustive.

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?

It is a single dense paragraph that front-loads purpose, then paging semantics, then auth requirements — a sensible order with little wasted text. The phrase 'and more' is slightly loose where the schema already enumerates categories, and the clause 'offset pages on or state_category narrows' is a bit compressed.

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?

An output schema exists, so return values need no explanation, and the description covers the remaining essentials: ownership scope, category grouping, per-category pagination behavior, and authentication requirements. Nothing an agent needs in order to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds non-obvious meaning: limit and offset apply within each category rather than across the whole result set, which the schema alone does not make clear. That per-category paging semantics is exactly the kind of clarification that prevents miscalls.

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 names a specific verb and resource — the caller's own listings — and adds a plain-language gloss ('show the tickets I'm selling') plus the organizing concept (grouped by lifecycle category). The word 'own' plus the category grouping distinguishes it from marketplace-facing siblings like get_ticket_listings or list_open_listings without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains how the result is shaped and how to narrow it ('state_category narrows to one category'), which implicitly tells the agent when to use the filter. However, it never states when to pick this over sibling tools such as get_my_listing_status or list_open_listings, so routing is left to inference.

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