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

etsy-clean-mcp

by phobicdotno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_listing

Read-only

Retrieve a single Etsy listing by ID, including details, images, and inventory data such as products, prices, quantities, and SKUs.

Instructions

One listing with details, images and inventory (products, prices, quantities, SKUs).

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": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYesListing id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description usefully discloses the returned content—details, images, products, prices, quantities, and SKUs—but says nothing about permissions, not-found behavior, or freshness.

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?

It is a single compact sentence with no wasted wording and front-loads the singular-listing scope. The fragmentary style ('One listing with...') is terse but readable.

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 simple one-parameter read tool with complete schema coverage and read-only annotations, the description covers the main return contents. It omits expected failure behavior and any distinction from related listing tools, leaving some operational gaps.

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?

The only parameter, listing_id, is fully documented in the schema with its positive-integer constraint. The description adds no additional meaning about the identifier beyond implicit reference to a listing.

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 identifies the resource and scope precisely: one listing, including details, images, and inventory. It lacks an explicit verb such as 'retrieve' or 'fetch,' but singular 'one listing' distinguishes it from sibling list_listings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus list_listings, update_listing, or update_inventory. The single-listing scope is implied by the wording, but no alternatives or conditions are stated.

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