Skip to main content
Glama

Create a listing draft

create_draft
Idempotent

Create a reviewable listing draft with condition-based price suggestions and duplicate-listing warnings; it never publishes and reuses idempotency keys to prevent duplicate drafts.

Instructions

Create a listing DRAFT for the seller to review. It never publishes anything. If pricePen is omitted, the suggested price is used. Reusing an idempotencyKey returns the existing draft instead of creating another. The result includes warnings, e.g. when the same card is already listed.

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": {
      "productId": "<productId>",
      "condition": "<condition>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
subTypeNoPrice sub-type used for the suggestion
languageNoEnglish
pricePenNoPrice set by the seller, in soles
quantityNo
conditionYesCard condition: NM, LP, MP, HP or DMG
productIdYesproductId from search_cards
idempotencyKeyYesStable key for this draft, e.g. '<runId>-<productId>-<condition>-<language>'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare non-readOnly, idempotent, non-destructive, closed-world, but the description adds genuinely new behavior: nothing is ever published, reusing an idempotencyKey returns the existing draft rather than duplicating, and the result carries warnings such as a duplicate card already being listed. That is exactly the mutation-safety and return-content context 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each carrying a distinct fact (scope, no-publish guarantee, price default, idempotency, result warnings). The non-publishing guarantee is front-loaded and there is no filler or repetition.

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 no output schema, the description correctly notes that the result includes warnings, and it covers the two most consequential behaviors (idempotency reuse and price defaulting). The 7-parameter surface is only partly explained — subType in particular stays opaque — so it is close to complete but not fully.

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 71% and the schema documents pricePen as a seller-set price in soles, but the description adds the meaningful fallback rule that omitting it triggers the suggested price. It also clarifies the intended reuse semantics of idempotencyKey beyond the schema's example format. subType and language are left to the schema, so this is strong but not exhaustive.

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?

"Create a listing DRAFT for the seller to review" gives a specific verb (create) and resource (listing draft) plus the scoping constraint that it never publishes. An agent can immediately tell this apart from list/search siblings and from any publish action, without opening 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 Guidelines4/5

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

The description establishes the context for use (draft for seller review, non-publishing) and indirectly routes price discovery by saying the suggested price is used when pricePen is omitted. It does not explicitly name an alternative such as suggest_price for cases where the caller wants the price first, so it stops short of full when/when-not guidance.

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