Skip to main content
Glama
Sign In

commercebridge

by io.github.IsaiahDupree
OverviewDiscussionsAdmin

Get up to 20 eBay items in one call

get_ebay_items
Read-onlyIdempotent

Bulk-fetch full item detail for up to 20 eBay items in a single call, given comma-separated item ids. Returns an honest credentials_required error until the upstream deployment has eBay app credentials provisioned.

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_ids": "<item_ids>"
    },
    "name": "get_ebay_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoDefault us.
item_idsYesComma-separated eBay item ids (max 20). Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds the credential dependency, warning that a `credentials_required` error will be returned until credentials are provisioned, which is valuable behavioral context beyond the annotations.

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 sentences, both purposeful: one describes the core function, the other a relevant operational caveat. No redundant words.

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?

With only 2 parameters and rich annotations, the description addresses the main functionality and the credential error. It does not specify return structure, but no output schema exists, and the phrase 'full item detail' hints at the return. Adequate for the tool's simplicity.

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 covers both parameters with descriptions, including the required comma-separated item_ids with max 20 and the optional country enum. The description merely reiterates the schema details without adding new semantics, so baseline 3 applies.

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

Purpose5/5

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

The description uses a specific verb 'Bulk-fetch' and identifies the resource 'full item detail for up to 20 eBay items in a single call', clearly distinguishing from the singular sibling tool get_ebay_item. The title reinforces the batch capability.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies batch usage with 'Bulk-fetch' and 'up to 20', but does not explicitly contrast with get_ebay_item or specify when not to use. There are no alternative tool references or exclusions.

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

All commercebridge 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