Skip to main content
Glama
Sign In
etsy-clean-mcp

etsy-clean-mcp

by phobicdotno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

update_inventory

Set price, quantity, and SKU per product on an Etsy listing. Preview the full inventory change first, then confirm to send it, so you can verify updates before they go live.

Instructions

Set price, quantity and/or SKU per product. Omit product_id when the listing has a single product. confirm=false reads the current inventory and previews the full update.

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>",
      "changes": "<changes>"
    },
    "name": "update_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
confirmNofalse (default) only returns a preview of the request. true sends it.
listing_idYesListing id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the materially important detail that confirm=false performs a read-and-preview rather than a write, so the agent knows the default invocation is non-destructive despite the mutation annotation. It does not disclose what a confirmed call returns or how partial failures across multiple products behave.

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?

Three short sentences, front-loaded with the operation, then the riskiest parameter rule, then the safety mode. No filler or redundancy.

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?

For a batch mutation with no output schema, the description covers the preview/send model but says nothing about what a confirmed update returns, how multi-product changes behave on partial failure, or the role of readiness_state_id. Those gaps matter for an agent deciding whether to batch several products into one call.

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?

Beyond the 67% schema coverage, the description adds genuinely non-obvious semantics: the changes array is interpreted per product, and product_id may be omitted for single-product listings. The confirm description largely restates the schema, and readiness_state_id is not addressed at all, keeping it short of a 5.

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?

The description opens with a specific verb and resource set: 'Set price, quantity and/or SKU per product', which clearly scopes it to inventory fields rather than general listing metadata. It does not explicitly name a contrasting sibling (e.g., update_listing), but the field-level specificity makes the distinction inferable.

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 a concrete conditional rule ('Omit product_id when the listing has a single product') and explains the two-mode workflow via confirm. It stops short of naming alternatives or stating when not to use this tool versus update_listing, so it is clear context without exclusions.

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

Deploy Server

Other Tools