Skip to main content
Glama

Nexscope Ecommerce Data MCP

eBay Product Research: search API

nexscope_data_ebay_search
Read-only

eBay Product Research: search API.

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_data_ebay_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, used for pagination
keywordNoSearch keywords, maximum 1024 characters; required unless categoryId is supplied
noCacheNoWhether to disable caching
orderByNoSort by. Optional values: `1` (soon to end), `2` (lowest price), `3` (highest price), `7` (closest), `10` (latest on the shelves), `12` (best match), `15` (lowest price + shipping fee), `16` (highest price + shipping fee), `18` (new product first), `19` (second-hand priority)
prefLocNoPreferred location range. Optional values: `1` (national), `2` (regional), `3` (global)
zipCodeNoZIP or postal code to filter products for delivery by area
locationNoThe country/region code where the product is located, for example: `1` (United States), `2` (Canada), `3` (UK), `45` (China), `77` (Germany)
pageSizeNoThe maximum number of results returned per page. Optional values: `25`, `50`, `100`, `200`
priceMaxNoHighest price filter
priceMinNoLowest price filter
showOnlyNoFilter conditions, multiple values separated by commas. Optional values: `Complete` (Ended), `FR` (Free Returns), `RPA` (Returns Accepted), `AS` (Authorized Seller), `Savings` (discount), `SaleItems` (promotional items), `Lots` (bulk), `Charity` (charity), `AV`, `FS` (free shipping), `LPickup` (self-pickup)
categoryIdNoeBay category ID, used to search for specified categories; required unless keyword is supplied
ebayDomainNoeBay site domain name. Optional values: `ebay.com` (United States), `ebay.co.uk` (UK), `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)
buyingFormatNoPurchase format. Optional values: `Auction` (auction), `BIN` (fixed price), `BO` (best offer)
itemConditionNoProduct status code, multiple separated by `\|`. Optional values: `1000` (new), `1500` (new other), `1750` (new with defects), `2000` (official refurbished), `2010` (excellent refurbished), `2020` (Good Refurbished), `2030` (Generally Refurbished), `2500` (Seller Refurbished), `2750` (Almost New), `3000` (Second Hand/Used), `7000` (Accessory or Not Working)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / categoryId / description
      Previous value: -"eBay category ID, used to search for specified categories"New value: +"eBay category ID, used to search for specified categories; required unless keyword is supplied"
    • changedInput schema / properties / keyword / description
      Previous value: -"Search keywords, maximum 1024 characters"New value: +"Search keywords, maximum 1024 characters; required unless categoryId is supplied"
  2. Changed2 schema fields changed
    • changedInput schema / properties / showOnly / description
      Previous value: -"Filter conditions, multiple values separated by commas. Optional values: `Complete` (Ended), `Sold` (Sold), `FR` (Free Returns), `RPA` (Returns Accepted), `AS` (Authorized Seller), `Savings` (discount), `SaleItems` (promotional items), `Lots` (bulk), `Charity` (charity), `AV`, `FS` (free shipping), `LPickup` (self-pickup)"New value: +"Filter conditions, multiple values separated by commas. Optional values: `Complete` (Ended), `FR` (Free Returns), `RPA` (Returns Accepted), `AS` (Authorized Seller), `Savings` (discount), `SaleItems` (promotional items), `Lots` (bulk), `Charity` (charity), `AV`, `FS` (free shipping), `LPickup` (self-pickup)"
    • changedInput schema / properties / showOnly / pattern
      Previous value: -"^(?:Complete|Sold|FR|RPA|AS|Savings|SaleItems|Lots|Charity|AV|FS|LPickup)(?:,(?:Complete|Sold|FR|RPA|AS|Savings|SaleItems|Lots|Charity|AV|FS|LPickup))*$"New value: +"^(?:Complete|FR|RPA|AS|Savings|SaleItems|Lots|Charity|AV|FS|LPickup)(?:,(?:Complete|FR|RPA|AS|Savings|SaleItems|Lots|Charity|AV|FS|LPickup))*$"
  3. Changed3 schema fields changed
    • changedInput schema / properties / buyingFormat / enum
      Previous value: -[
      -  "BIN",
      -  "BO"
      -]New value: +[
      +  "Auction",
      +  "BIN",
      +  "BO"
      +]
    • removedInput schema / properties / showOnly / enum
      Removed value: -[
      -  "FR",
      -  "RPA",
      -  "AS",
      -  "AV",
      -  "FS"
      -]
    • addedInput schema / properties / showOnly / pattern
      Added value: +"^(?:Complete|Sold|FR|RPA|AS|Savings|SaleItems|Lots|Charity|AV|FS|LPickup)(?:,(?:Complete|Sold|FR|RPA|AS|Savings|SaleItems|Lots|Charity|AV|FS|LPickup))*$"
  4. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing on top of that — no mention of result limits, pagination depth, rate limits, or quota behavior for a 15-parameter query tool.

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

Conciseness3/5

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

The sentence contains no filler and is front-loaded, but it is under-specified rather than concise — it is a title echo that would take two or three sentences to become useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 15 parameters, rich enum-like filters and no output schema, the description provides no information an agent could act on. Everything the agent needs comes from the schema and annotations, leaving the description effectively empty.

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%, so every parameter including enums for orderBy, showOnly, buyingFormat and itemCondition is already documented. The description contributes no additional semantics, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the title almost verbatim ('eBay Product Research: search API') and never says what is actually searched or returned. It does imply a search over eBay product data, but gives no verb-level specificity and nothing distinguishes it from the sibling nexscope_ebay_search.

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 when-to-use, when-not-to-use, or alternative-tool guidance of any kind. An agent must infer from the name alone whether this or nexscope_ebay_search is appropriate.

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