Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ebay_seller_shop

Fetch item listings from a given eBay seller's shop, page by page, including prices, bids, and watchers.

Instructions

Get eBay seller shop listings. Lists the items in an eBay seller's shop, identified by the required seller username, one page at a time with page (default 1). Each result has its item id, title, link, image, price or price range, shipping note, location, bid count and watcher count. The response gives the total and a has_more flag.

Input Schema

NameRequiredDescriptionDefault
pageNoShop page number
sellerYeseBay seller username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden — and it largely meets it. It enumerates the returned item fields (id, title, link, image, price or price range, shipping note, location, bid count, watcher count) and the response envelope (`total`, `has_more`), which is exactly what an agent needs since there is no output schema. It stops short of auth, rate-limit, or cost disclosure, which is why this is a 4 rather than 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences: what it does, how to identify/paginate, what comes back. The field enumeration is long but earns its place because no output schema exists to carry that information.

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 two-parameter read tool with no annotations and no output schema, the description covers purpose, the scoping parameter, pagination default, and the full return shape. Only ancillary concerns (auth, rate limits, error behavior) are unaddressed, so it is nearly complete.

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 100%, so the baseline would be 3, but the description adds the default value for `page` ('default 1') and reinforces that `seller` is required — details that go beyond the bare schema strings ('Shop page number', 'eBay seller username'). It adds real, if modest, value.

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 and resource ('Get eBay seller shop listings') and immediately narrows the scope to items in a shop keyed by the required `seller` username. This cleanly separates it from ebay_search (keyword search), ebay_item (single item), ebay_seller / ebay_seller_about (seller profile metadata) even though no sibling is named.

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?

Usage is implied by the scope statement rather than stated: an agent infers 'use this to enumerate a seller's inventory.' It supplies operating context (seller is required, results come one page at a time via `page`), but gives no when-not guidance or routing to alternatives such as ebay_search when the seller is unknown.

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