Skip to main content
Glama
Sign In
NeuralVerge

NeuralVerge

Official
by neuralverge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

run_ebay_item

Fetch full eBay listing details by item ID—title, price, condition, images, and seller—to inspect or validate an item before purchase.

Instructions

Get full eBay listing details by item ID: title, price, condition, images, and seller. Flat 5 points per successful run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "<item>"
    },
    "name": "run_ebay_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesItem ID or URL. e.g. 336776720041

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.2/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 behavioral burden. It does disclose the cost model ('Flat 5 points per successful run'), which is genuine value beyond the schema, and lists returned fields. However it says nothing about authentication, rate limits, pagination, or failure behavior, so the transparency is partial.

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?

Two tight sentences that front-load the purpose before the call. The price note is short and earns its place, though it reads as bolted on rather than integrated.

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 single-parameter read tool with no output schema, the description usefully enumerates the returned fields and the cost, which is close to sufficient. It is missing the disambiguation from run_ebay_product/run_ebay_item_search that a packed eBay sibling set would warrant.

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 coverage is 100%, so the single 'item' parameter is already fully documented, including that it accepts an ID or a URL. The description only echoes 'by item ID' and actually omits the URL form, adding no meaning beyond the schema. 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 and resource ('Get full eBay listing details by item ID') and enumerates the returned fields, so the agent knows exactly what it retrieves. It doesn't disambiguate against the close siblings run_ebay_product or run_ebay_item_search, which look up nearly the same thing, leaving a residual selection ambiguity.

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 phrase 'by item ID' implies you must already have an identifier, but the description never says when to use this versus run_ebay_item_search (search) or run_ebay_product. No prerequisites, no exclusions, no alternatives are stated.

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