Skip to main content
Glama

Nexscope Ecommerce Data MCP

Ebay Search

nexscope_ebay_search
Read-only

Search and browse product listings across multiple eBay international sites. Trigger when user mentions eBay product search, eBay listing query, eBay price comparison, eBay market browsing, eBay sold items, eBay auction search, eBay product research, eBay products, eBay pricing, eBay competitors, eBay auctions, eBay market analysis — even if "eBay" is not explicitly mentioned, as long as the need involves searching products on eBay, comparing eBay prices, finding sold listings, or analyzing eBay market data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nexscope_ebay_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination, default 1
keywordNoSearch keyword, max 1024 characters; required unless categoryId is supplied
noCacheNoWhether to bypass cache, default false
orderByNoSort order, default 12 (Best Match). Options: 1 (Ending soonest), 2 (Price lowest), 3 (Price highest), 7 (Distance nearest), 10 (Newly listed), 12 (Best Match), 15 (Price + shipping lowest), 16 (Price + shipping highest), 18 (New first), 19 (Used first)
prefLocNoPreferred location scope. Options: 1 (Domestic), 2 (Regional), 3 (Worldwide)
zipCodeNoZIP or postal code for filtering shippable items by region
locationNoCountry/region code of item location (e.g., 1=United States, 2=Canada, 3=United Kingdom, 45=China, 77=Germany)
pageSizeNoMaximum results per page, default 50. Options: 25, 50, 100, 200
priceMaxNoMaximum price filter
priceMinNoMinimum price filter
showOnlyNoFilter conditions, comma-separated for multiple values. Options: Complete (Ended), FR (Free returns), RPA (Returns accepted), AS (Authorized seller), Savings (Discounts), SaleItems (Sale items), Lots (Lots), Charity (Charity), AV, FS (Free shipping), LPickup (Local pickup)
categoryIdNoeBay category ID for category-specific search; required unless keyword is supplied
ebayDomainNoeBay site domain, default ebay.com. Options: ebay.com (United States), ebay.co.uk (United Kingdom), ebay.de (Germany), ebay.fr (France), ebay.it (Italy), ebay.es (Spain), ebay.ca (Canada), ebay.com.au (Australia), ebay.nl (Netherlands), ebay.at (Austria), ebay.ch (Switzerland), ebay.pl (Poland), ebay.ie (Ireland), ebay.com.hk (Hong Kong, China), ebay.com.my (Malaysia), ebay.com.sg (Singapore)
buyingFormatNoBuying format. Options: Auction, BIN (Buy It Now), BO (Best Offer)
itemConditionNoItem condition codes separated by |. Options: 1000, 1500, 1750, 2000, 2010, 2020, 2030, 2500, 2750, 3000, 7000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / categoryId / description
      Previous value: -"eBay category ID for category-specific search"New value: +"eBay category ID for category-specific search; required unless keyword is supplied"
    • changedInput schema / properties / keyword / description
      Previous value: -"Search keyword, max 1024 characters"New value: +"Search keyword, max 1024 characters; required unless categoryId is supplied"
  2. Changed1 schema field changed
    • changedInput schema / properties / showOnly / description
      Previous value: -"Filter conditions, comma-separated for multiple values. Options: Complete (Ended), Sold (Sold), FR (Free returns), RPA (Returns accepted), AS (Authorized seller), Savings (Discounts), SaleItems (Sale items), Lots (Lots), Charity (Charity), AV, FS (Free shipping), LPickup (Local pickup)"New value: +"Filter conditions, comma-separated for multiple values. Options: Complete (Ended), FR (Free returns), RPA (Returns accepted), AS (Authorized seller), Savings (Discounts), SaleItems (Sale items), Lots (Lots), Charity (Charity), AV, FS (Free shipping), LPickup (Local pickup)"
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results span multiple international sites and include sold/auction listings, which is real behavioral context. It says nothing about result caps, pagination limits, caching (the noCache parameter implies one), or auth/quota constraints, so it adds only modest value beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The opening sentence is well front-loaded, but the remaining text is a flat, repetitive keyword list ("eBay product search, eBay listing query, eBay price comparison, eBay market browsing, eBay sold items, eBay auction search...") with heavy redundancy between "eBay products/pricing/auctions" and the phrases around them. Most of that enumeration could be collapsed into two or three clauses without losing routing signal.

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 15-parameter search tool with no output schema and a large enum surface, the description covers when to call but not what comes back — no indication of result shape, listing fields, or whether sold-listing data differs from active-listing data. Combined with no explanation of the caching or pagination behavior implied by noCache/page/pageSize, it is adequate but leaves real 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?

Schema description coverage is 100%, with every one of the 15 parameters documented including enum option lists, so the schema carries the burden and the baseline of 3 applies. The description contributes no meaning about any parameter and does not clarify the keyword-vs-categoryId requirement tradeoff that the schema only partially implies.

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 first sentence gives a specific verb and resource ("Search and browse product listings across multiple eBay international sites"), which is far better than the tautological title. It does not distinguish itself from the near-identical sibling nexscope_data_ebay_search, so an agent has no basis for choosing between the two from the description alone.

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

Usage Guidelines4/5

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

The trigger clause enumerates concrete use contexts (product search, price comparison, sold listings, auction search, market analysis) and explicitly widens scope to implicit eBay intent, which is genuinely useful routing guidance. It stops short of a 5 because it never says when NOT to use the tool and names no alternative for the overlapping eBay sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources