Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

etsy_listing

Fetch detailed Etsy listing data by numeric ID, including title, price, currency, quantity, views, favorites, tags, images, category, shop info, and status flags.

Instructions

Get Etsy listing detail. Returns the details of one Etsy listing by its numeric id: title, description, URL, price and currency, quantity, favorites, views, materials, tags, images and category. It also has the shop id and name, listing state, sold-out, customizable and digital flags, when it was made, shipping origin country, and create and update dates.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Etsy listing id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are present, so the description carries the behavioral burden. The verb 'Get' implies a read-only, non-destructive operation and the description lists returned fields, but it does not state permissions, rate limits, error behavior, or side effects. This is minimum viable for a simple detail endpoint.

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?

Front-loaded with a clear purpose sentence, followed by a compact enumeration of returned fields. The second sentence is somewhat long but justified because no output schema exists; no obvious filler.

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?

Given no output schema, the description thoroughly documents the return payload (title, price, images, shop info, flags, dates, etc.), which is exactly what an agent needs to interpret results. It is complete for a single-resource detail lookup.

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 coverage is 100% and the single 'id' parameter is already documented as 'Numeric Etsy listing id' in the schema. The description repeats that it is a numeric id but adds no syntax, format, or validation detail beyond the schema.

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?

States a specific verb and resource ('Get Etsy listing detail') and the required identifier. However, it does not explicitly differentiate itself from closely named siblings like etsy_listing_reviews or etsy_shop_listings, leaving the agent to infer that it returns the core listing record.

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?

No when-to-use guidance, no alternatives, and no prerequisites are mentioned. The agent is only told to supply a numeric id; the description does not say when to choose this tool over etsy_search or etsy_shop_listings.

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