Skip to main content
Glama

Edit a listing

update_listing
Destructive

Change an existing listing's title, description or tags, or a seller product's price and compare-at price. Description is plain text (blank lines start new paragraphs). Only listings from list_my_listings. 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": {
      "listing_id": "<listing_id>"
    },
    "name": "update_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
titleNo
price_usdNoSeller products with a single price only
listing_idYes
descriptionNo
compare_at_price_usdNoStrikethrough "was" price; null removes it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=false, so the agent knows this is a mutating, non-idempotent call. The description adds two genuinely useful traits beyond that: the connected-account requirement and the constraint that only listings sourced from list_my_listings may be edited. It does not state whether omitted fields are left intact or cleared, nor what happens on a failed edit, which matters for a destructiveHint=true mutation.

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?

Three sentences, front-loaded with the mutable fields and followed by constraints, with no filler. The parenthetical on paragraph breaks is well placed and short. Minor cost: the price clause is slightly compressed and needs a second read to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and annotations cover the safety profile, so the description carries the burden for mutation semantics and prerequisites, which it does for account and source scope. For a six-parameter destructive update it should still say whether fields not supplied are left unchanged and whether compare-at price removal requires the null the schema mentions.

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 description coverage is only 33%, and the description compensates partially: it explains that price_usd/compare_at_price_usd apply only to seller products with a single price, and that description is plain text where blank lines start new paragraphs. That is real meaning beyond the schema. listing_id, title and tags get no added semantics, and the crucial 'are unspecified fields preserved?' question tied to the non-required parameters is left unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Change an existing listing's title, description or tags, or a seller product's price and compare-at price" gives a specific verb plus the exact set of mutable fields, and it distinguishes the two object kinds (listing vs. seller product). It is clearly an edit operation and not a create/pause/resume, so it separates from siblings by behavior even though no sibling is named.

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?

"Only listings from list_my_listings" and "Needs a connected Printlooper account" give a clear scope restriction and a prerequisite, which is more than most update tools state. It stops short of saying when to prefer pause_listing/resume_listing or create_listing_draft instead, so a mild gap remains.

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