Skip to main content
Glama

Newegg products search

run_newegg_products_search
Read-onlyIdempotent

Search Newegg products by keyword with sort: price, rating, seller and stock. 1 point per returned record.

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": {
      "keyword": "<keyword>"
    },
    "name": "run_newegg_products_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Options: 1 = Lowest price, 2 = Highest price, 3 = Best selling, 4 = Best rating, 5 = Most reviews
keywordYesSearch term. e.g. logitech g502
max_itemsNoMax items (up to 500) Default: 25.
start_pageNoStarting page Default: 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context the annotations cannot carry: the credit cost ('1 point per returned record'), which matters for a tool that can return up to 500 items. It stops short of pagination or result-cap behavior.

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 compact sentences, keyword search front-loaded, cost note trailing as the secondary detail. No filler, though the parenthetical sort list is where the imprecision creeps in.

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 simple read-only search with full schema coverage and no output schema, this is adequate: purpose, sort dimension, and cost are present. It lacks any pagination note (start_page/max_items limits) and any sibling routing, which would round out a directory where dozens of near-identical *_products_search tools compete.

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% and the enum fully documents the sort options, so the schema carries the parameter burden and a 3 is the baseline. However, the description's sort summary ('price, rating, seller and stock') does not match the actual enum values (price, selling, rating, reviews), introducing slight inaccuracy that the schema must correct.

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 (search) plus resource (Newegg products) and the keyword input, which cleanly separates it from siblings like run_newegg_products (detail), run_newegg_products_offers, and run_newegg_sellers. It never explicitly names those siblings, but the search semantics are unambiguous.

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?

No when-to-use guidance, no prerequisites, and no routing information relative to the many Newegg siblings (products, offers, reviews, categories_products). The agent must infer from the name alone that this is the keyword-search entry point.

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