Skip to main content
Glama
taka392
by taka392

get_item_summary

Retrieves a summary of an eBay listing using the item's REST ID, enabling browsing of single item details.

Instructions

GET a single Browse listing by REST item id (encode-safe; pass the v1 item id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool registration via @mcp.tool() decorator on get_item_summary
    @mcp.tool()
    def get_item_summary(item_id: str) -> Dict[str, Any]:
  • MCP tool handler that delegates to the EbayClient implementation
    def get_item_summary(item_id: str) -> Dict[str, Any]:
        """GET a single Browse listing by REST item id (encode-safe; pass the v1 item id)."""
        return _client().get_item_summary(item_id)
  • Core implementation: makes GET request to eBay Browse API /buy/browse/v1/item/{encoded_item_id}
    def get_item_summary(self, item_id: str) -> Dict[str, Any]:
        """Retrieve a single Browse item representation by RESTful item Id."""
        rid = item_id.strip()
        if not rid:
            raise EbayError("item_id must not be empty")
        enc = quote(rid, safe="")
        url = f"{self.api_root}/buy/browse/v1/item/{enc}"
        data = self._request_json("GET", url, retry_refresh=True)
        if not isinstance(data, dict):
            raise EbayError(f"Unexpected item payload: {type(data)!r}")
        return data
Behavior2/5

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

No annotations exist, so the description bears full responsibility. It notes 'GET' implying read-only but omits authentication needs, error behavior, rate limits, or any side effects. The 'encode-safe' note adds minimal behavioral context.

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?

The description is a single, front-loaded sentence that conveys purpose and parameter hint without excess. It could include more behavioral detail without sacrificing conciseness.

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?

Given low complexity (1 param, output schema exists), the description is minimally adequate but lacks completeness regarding authentication, errors, and alternative tool use. With no annotations, more detail would be warranted.

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 0%, but the description adds 'REST item id' and 'encode-safe; pass the v1 item id', clarifying the parameter's type and encoding requirement beyond the bare schema property.

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 explicitly states it is a GET operation for a single Browse listing by REST item id, clearly distinguishing it from the sibling tool search_item_summary which implies searching rather than single-item retrieval.

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?

No explicit when-to-use or when-not-to-use guidance is provided. While the sibling tools suggest a search alternative, the description does not articulate selection criteria or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taka392/ebay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server