Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_item_by_legacy_id

Read-onlyIdempotent

Retrieve eBay item details using a classic numeric legacy item ID to resolve listings when only the legacy identifier is available.

Instructions

Get an eBay item by its legacy item ID (classic numeric ID).

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": {
      "client_id": "<client_id>",
      "client_secret": "<client_secret>",
      "legacy_item_id": "<legacy_item_id>"
    },
    "name": "ebay_get_item_by_legacy_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
marketplaceNo
client_secretYes
legacy_item_idYesLegacy eBay item ID (numeric)
legacy_variation_idNo
legacy_variation_skuNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds nothing further — no note that it requires client credentials, that it performs an authenticated external API call that may fail for expired/ended listings, or anything about response content.

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?

A single tight sentence with the key differentiator front-loaded and no filler. It is appropriately sized, though its brevity is partly the cause of the missing guidance.

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

Completeness2/5

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

For a six-parameter authenticated read tool with no output schema and 17% schema coverage, the description is too thin: it never explains the credential parameters, the marketplace scoping, or the two variation parameters that differentiate variant-level lookups from item-level ones.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%: of six parameters, only legacy_item_id is documented. The description usefully clarifies that this ID is classic/numeric, but says nothing about client_id, client_secret, marketplace, legacy_variation_id or legacy_variation_sku, leaving most of the surface undocumented in both places.

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 with the defining qualifier 'legacy item ID (classic numeric ID)', which distinguishes it from the sibling ebay_get_item. It stops short of explicitly contrasting the two, so the agent must infer that ebay_get_item is for modern IDs.

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 explicit when-to-use guidance or exclusion. The legacy-vs-modern distinction from ebay_get_item is implied by the parenthetical but never stated, so an agent holding an item ID has no instruction on which of the two eBay item tools to pick.

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