Skip to main content
Glama

Start a listing

create_listing_draft

Starts a listing from a ready staged model with the title, description, tags and price you suggest. Pass the shop, material and colors from get_listing_options when the user chose them, and the listing page starts on them. The user opens complete_url to confirm they own the rights, pick the shop and colors, add photos and publish. Nothing goes live until they do. Needs a connected Printlooper account.

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": {
      "file_id": "<file_id>",
      "title": "<title>"
    },
    "name": "create_listing_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
titleYes
colorsNoThe colors the user chose, each as hex and finish from get_listing_options
file_idYesA ready staged model id (file_...)
shop_idNoThe print shop the user chose, as shop.id from get_listing_options
materialNoThe material the user chose, for example PLA
price_usdNoSuggested retail price for sellers
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / colors
      Added value: +{
      +  "description": "The colors the user chose, each as hex and finish from get_listing_options",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "finish": {
      +        "maxLength": 20,
      +        "type": "string"
      +      },
      +      "hex": {
      +        "pattern": "^#[0-9a-fA-F]{6}$",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "hex"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / material
      Added value: +{
      +  "description": "The material the user chose, for example PLA",
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / shop_id
      Added value: +{
      +  "description": "The print shop the user chose, as shop.id from get_listing_options",
      +  "maxLength": 64,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare write, non-destructive, non-idempotent, closed-world. The description adds real context beyond them: the listing stays a draft and 'nothing goes live' until the user confirms rights, picks shop/colors, adds photos and publishes, plus the account-connection requirement and the returned complete_url. It does not address what happens on repeated calls (duplicate drafts), which is the one behavior an agent most needs given idempotentHint=false.

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 sentences, front-loaded with what the tool does and what it returns, then the human confirmation flow, then the account prerequisite. No sentence is redundant; 'Nothing goes live until they do' earns its place by resolving draft-vs-publish ambiguity.

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 supplies the key return artifact (complete_url) and what the user does with it, and it covers auth prerequisites and the option-sourcing rule for an 8-parameter mutation. An agent can call this correctly and hand off to the user without further information.

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?

All eight parameters are at least implied, and the description adds sourcing guidance the schema lacks: shop_id, material and colors should come from get_listing_options, while title/description/tags/price are 'you suggest.' With 63% schema coverage the description usefully fills the gap for the option-derived fields, though it adds nothing about price bounds or tag limits.

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 opens with a specific verb and resource: 'Starts a listing from a ready staged model,' plus the fields it accepts. That distinguishes it from start_model_upload (produces the staged model), update_listing (mutates an existing one) and add_listing_photos (post-creation step) without the agent opening a 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?

It gives clear preconditions: a ready staged model, a connected Printlooper account, and passing shop/material/colors from get_listing_options only 'when the user chose them.' It also explains the follow-up flow through complete_url. It stops short of explicitly naming the model-upload siblings as the required prior step, so the sequencing is inferred rather than stated.

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