Secondhand MCP

fetch

Read-onlyIdempotent

Retrieve full details of a secondhand marketplace listing using its ID from search results. Get complete information for a specific item by providing the marketplace-prefixed ID (e.g., facebook:12345).

Instructions

Fetch one listing in full for an id returned by the search tool, following the ChatGPT deep research tool contract. Id format: marketplace:listingId (for example "facebook:12345" or "ebay:v1|123|456"). Behavior: read-only. Errors: an id without the marketplace prefix, or for a removed listing, returns an error message. Not for: ids from search_marketplace, which take get_listing_details.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Result ID from the search tool (format: marketplace:listingId)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.7.1Sep 8, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds value beyond those by specifying error behavior for malformed ids and removed listings. The only minor redundancy is restating 'read-only' when annotations already provide it.

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?

The description is compact, front-loaded with the core purpose, then delivers id format, behavior, errors, and exclusions in a logical order. Every sentence earns its place and none are wasted.

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

Completeness5/5

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

For a single-parameter tool with no output schema, the description is complete: it specifies the id format with examples, explains error cases, declares read-only behavior, and routes the agent away from the wrong sibling tool. Nothing essential is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds further value by providing concrete id format examples ('facebook:12345' or 'ebay:v1|123|456') and by clarifying that ids from search_marketplace are not valid here. This goes beyond the schema's brief description.

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 states a specific verb and resource ('Fetch one listing in full') and immediately ties it to ids returned by the search tool. It also distinguishes itself from get_listing_details by explicitly saying what it is not for, so an agent can pick the correct tool without ambiguity.

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

Usage Guidelines5/5

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

The description clearly states when to use the tool: for ids returned by the search tool. It also gives an explicit exclusion and alternative: ids from search_marketplace should use get_listing_details instead. This is direct, actionable routing guidance.

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

Deploy Server