Skip to main content
Glama

Prepare a listing

prepare_listing

Prepares a listing for sale of a card the user owns (dealId from record_purchase, or cardId) on their connected selling account with its business policies. Nothing is listed yet. Returns the price (default: the 3 most recent sales average for a slab, the market price for a raw card; pass price to change it), quantity, the photo count with a one-time photo upload link (30 minutes) and a publishToken (15 minutes). Read the summary question to the user ("List at $X with N photos?"). When photos.count is above 0 the photos are saved: do not ask the user for more. To add or change photos the user uses the photo panel where one is shown, otherwise the uploadUrl; after photos change, call prepare_listing again before publish_listing. If the selling account isn't connected, the message says how. Where the assistant shows panels, the result opens a photo panel where the user can take the card's photo for the listing. If the result has alerts, show them to the user before anything else.

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

Input Schema

NameRequiredDescriptionDefault
priceNoThe listing price in USD (default: the suggested price).
titleNoA listing title (default: built from the card).
cardIdNoOr a card in the user's collection.
dealIdNoA Deal Desk purchase (from record_purchase).
quantityNoRaw cards: how many to list (default 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare a non-read-only, open-world, non-idempotent, non-destructive operation, and the description adds substantial context beyond that: nothing is published by this call, the upload link expires in 30 minutes, the publishToken in 15 minutes, alerts must be surfaced first, and the account-connection failure mode. This is exactly the operational detail the annotations cannot convey.

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?

Nearly every sentence carries actionable content, and the purpose plus the 'nothing is listed yet' caveat are front-loaded. The weakness is structural: one dense block of prose mixes return values, user-facing wording, photo handling, and error paths, so a scanning agent must read the whole paragraph to find the publish sequencing rule.

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?

With no output schema, the description takes on the burden of describing the return payload (price, quantity, photo count, upload URL with TTL, publishToken with TTL) and does so. For a multi-step, stateful preparation tool with five optional parameters, an agent has everything needed to call it, interpret the result, and know what to do next.

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 is 3, but the description genuinely adds meaning: the price default is derived from the 3 most recent slab sales or the raw-card market price, quantity applies to raw cards, and dealId is traced to record_purchase. Only 'title' is left entirely to the schema, which is a minor gap given the schema already documents it.

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 ('Prepares a listing for sale of a card the user owns') and immediately draws the boundary that matters most: 'Nothing is listed yet,' which separates it from publish_listing. It also names the two acceptable inputs (dealId from record_purchase, or cardId), so an agent can identify the tool without inspecting the 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?

Gives explicit sequencing rules (call prepare_listing again after photos change, before publish_listing), an interaction rule (read the summary question to the user, 'List <card> at $X with N photos?'), and a negative instruction (when photos.count > 0, do not ask the user for more). It also covers the fallback path when the selling account isn't connected.

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