etsy-clean-mcp

Overview Schema Source Related Servers Discussions Admin

update_listing

Edit Etsy listing details such as title, description, tags, materials, category, and profiles; preview changes before confirming. Price and quantity changes require update_inventory.

Instructions

Change listing text and settings (title, description, tags, materials, section, profiles, category). Not price/quantity: use update_inventory. confirm=false previews.

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

Name	Required	Description
`tags`	No	Up to 13 tags.
`title`	No
`confirm`	No	false (default) only returns a preview of the request. true sends it.
`who_made`	No
`is_supply`	No	true for craft supplies, false for finished products.
`materials`	No	Materials (letters, numbers, spaces).
`when_made`	No
`listing_id`	Yes	Listing id.
`description`	No	Full listing description.
`taxonomy_id`	No	Seller taxonomy id (see search_taxonomy).
`shop_section_id`	No	Shop section id (see list_shop_sections).
`return_policy_id`	No	Return policy id (see list_return_policies).
`should_auto_renew`	No
`shipping_profile_id`	No	Shipping profile id (see list_shipping_profiles).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Nov 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely new behavior: confirm=false is a dry-run preview, which is the key operational trait for a mutation tool. It does not mention permissions, rate limits, or whether omitted fields are preserved, which keeps it just short of a 5.

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?

Two compact sentences: scope first, then the exclusion/alternative, then the preview behavior. No filler, and the most decision-relevant information is front-loaded.

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?

For a 14-parameter mutation with no output schema, the description covers scope, the sibling boundary, and the dry-run flag, which is most of what an agent needs. It does not state whether unmentioned fields are left untouched on a partial update, a meaningful gap for an update tool, though annotations already carry the safety signals.

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%, so the baseline is 3, but the description adds meaning by grouping parameters into editable field families (text vs. settings) and by naming the concepts that map to shop_section_id, taxonomy_id and the profile ids. It also clarifies that confirm=false previews rather than sends, reinforcing the schema note.

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 (Change) and resource (listing text and settings), then enumerates the covered field groups: title, description, tags, materials, section, profiles, category. It also explicitly differentiates itself from update_inventory by excluding price/quantity, so an agent can separate the two mutation tools without 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 Guidelines5/5

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

Provides an explicit when-not with a named alternative: 'Not price/quantity: use update_inventory.' It also gives the operational rule that confirm=false previews before sending, which tells the agent how to invoke it safely on the first attempt.

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

Deploy Server