Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ebay_seller_feedback

Retrieve an eBay seller's feedback count, positive percentage, rating summary, detailed ratings, and buyer review cards by username, with page controls for browsing results.

Instructions

Get eBay seller feedback. Returns the feedback eBay shows for a seller, identified by the required seller username. The response has the total feedback count, positive feedback percentage, overall rating summary, detailed seller ratings, and review cards with buyer, comment, rating, period and verified-purchase flag. Page with page (default 1) and per_page (24, 48 or 72; default 48), using has_more and next_page.

Input Schema

NameRequiredDescriptionDefault
pageNoFeedback page number
sellerYeseBay seller username
per_pageNoReviews per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / per_page / enum
      Added value: +[
+  24,
+  48,
+  72
+]
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned fields (total count, positive percentage, rating summary, detailed seller ratings, review cards) and the pagination mechanism (has_more, next_page). It omits auth requirements and rate limits, which keeps it from 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?

Front-loaded with the purpose, then the return shape, then pagination – a logical order with no filler sentences. It is dense but every clause conveys distinct 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?

No output schema exists, so the description must describe returns, which it does thoroughly, and it covers all three params and pagination. It is complete for a read tool, with only minor gaps (no auth/permission notes).

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 baseline is 3, but the description adds real meaning beyond the schema: the defaults for `page` (1) and `per_page` (48), the allowed enum values (24/48/72), and the pagination flow via `has_more`/`next_page`. This is genuine added value over the bare 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+resource ('Get eBay seller feedback') and identifies the required `seller` username, so the agent knows exactly what is fetched. It does not explicitly differentiate from close siblings like ebay_seller, ebay_seller_about, or ebay_seller_shop, so it falls short of a 5.

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 explicit when-to-use guidance or routing to alternatives, despite several sibling tools covering the same seller (ebay_seller_about, ebay_seller_shop). The purpose implies usage but the definition never states when this tool is preferred over them.

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