Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ebay_item

Retrieve detailed eBay listing data by item ID, including price, condition, images, seller, shipping, and ratings for product research or monitoring.

Instructions

Get eBay item details. Returns the details of one eBay listing by item_id: title, link, images, price and price text, condition, availability, item specifics, description, location and shipping. It also carries the seller's name, store, feedback score, followers and items sold, along with the listing's rating and rating count.

Input Schema

NameRequiredDescriptionDefault
item_idYeseBay item ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and clearly establishes a read/retrieval operation. It enumerates returned fields extensively, including seller and rating information, though it omits auth requirements, rate limits, error behavior, and response format details.

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?

The description is two sentences and front-loads the purpose before listing return contents. Every sentence adds useful information with no filler.

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?

Because there is no output schema, the field enumeration is valuable and covers most of what an agent needs to know about the response. It is largely complete for an item-detail tool, though error/auth/availability notes are absent.

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 single parameter is fully documented in the schema as 'eBay item ID', and the description repeats that the lookup is by item_id. It adds no format, example, source, or constraints beyond what the schema already provides, so baseline 3 is appropriate.

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 states a specific verb and resource: get eBay item details for one listing by item_id. An agent can tell this is a detail lookup rather than a search, but the description does not explicitly name sibling tools such as ebay_search or ebay_seller to sharpen routing.

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

Usage Guidelines3/5

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

The scope implies usage: call this when you already have an eBay item_id and need details for that single listing. However, it gives no explicit when-to-use/when-not guidance, no alternatives, and no note on where item_id should come from.

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