Skip to main content
Glama

NeuralVerge Business Intelligence

by ai.neuralverge.api
OverviewDiscussionsAdmin

eBay item search

run_ebay_item_search

Search active eBay listings by keyword: title, price, condition, and seller summary. 1 point per returned record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort by. Options: ending_soonest = Ending soonest, newly_listed = Newly listed, price_low = Price: low to high, price_high = Price: high to low
keywordYesSearch term. e.g. wireless mouse
conditionNoCondition. Options: new = New, open_box = Open box, used = Used, parts = For parts / not working
max_itemsNoMax items (up to 500) Default: 25.
max_priceNoMax price
min_priceNoMin price
start_pageNoStarting page Default: 1.
category_idNoCategory ID. e.g. 58058
buying_formatNoBuying format. Options: auction = Auction, buy_it_now = Buy It Now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category_id / description
      Previous value: -"Category ID. e.g. e.g. 58058"New value: +"Category ID. e.g. 58058"
  2. Changed12 schema fields changed
    • changedInput schema / properties / buying_format / description
      Previous value: -"Buying format filter."New value: +"Buying format. Options: auction = Auction, buy_it_now = Buy It Now"
    • changedInput schema / properties / category_id / description
      Previous value: -"eBay category ID to search within (see run_ebay_category)."New value: +"Category ID. e.g. e.g. 58058"
    • changedInput schema / properties / condition / description
      Previous value: -"Item condition filter."New value: +"Condition. Options: new = New, open_box = Open box, used = Used, parts = For parts / not working"
    • changedInput schema / properties / keyword / description
      Previous value: -"Search term, e.g. 'wireless mouse'."New value: +"Search term. e.g. wireless mouse"
    • changedInput schema / properties / max_items / description
      Previous value: -"Maximum number of items to return (1-500, default 25). Billed at 1 point per returned record."New value: +"Max items (up to 500) Default: 25."
    • changedInput schema / properties / max_price / description
      Previous value: -"Maximum price, in USD."New value: +"Max price"
    • removedInput schema / properties / max_price / minimum
      Removed value: -0
    • changedInput schema / properties / min_price / description
      Previous value: -"Minimum price, in USD."New value: +"Min price"
    • removedInput schema / properties / min_price / minimum
      Removed value: -0
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order (default best_match)."New value: +"Sort by. Options: ending_soonest = Ending soonest, newly_listed = Newly listed, price_low = Price: low to high, price_high = Price: high to low"
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "best_match",
-  "ending_soonest",
-  "newly_listed",
-  "price_low",
-  "price_high"
-]New value: +[
+  "ending_soonest",
+  "newly_listed",
+  "price_low",
+  "price_high"
+]
    • changedInput schema / properties / start_page / description
      Previous value: -"Result page to start from (default 1)."New value: +"Starting page Default: 1."
  3. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses two behavioral facts: results are limited to *active* listings (not sold/closed), and each returned record costs 1 point. However, it omits pagination behavior (there is a start_page param), rate limits, and any auth/result-format detail.

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?

Two tight sentences with zero waste; the core action is front-loaded and the point-cost caveat follows immediately. Nothing could be cut without losing information.

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 9-parameter search tool with no annotations and no output schema, the description partially compensates by naming returned fields and the point cost, but it leaves pagination (start_page/max_items interaction) and result-set behavior unexplained. Adequate but incomplete.

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 the schema already documents all 9 parameters, including enum options and defaults. The description names keyword and condition as concepts but adds no syntax, format, or defaulting information beyond what the schema provides — the baseline 3 applies.

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 (search active eBay listings) plus keyword scope and the fields returned (title, price, condition, seller summary). It is distinguishable from run_ebay_item semantically, but it never names or contrasts the adjacent eBay siblings (run_ebay_seller_items, run_ebay_item), so it stops short of full sibling differentiation.

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?

The description says nothing about when to use this search versus run_ebay_item, run_ebay_product, run_ebay_seller_items, or the search tools of other marketplaces. No prerequisites, no exclusions, no alternative routing is offered.

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

All NeuralVerge Business Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources