Fetch Mercari's curated home feed and return listing summaries with title, price, thumbnail, condition, and seller details for quick browsing.
Get Mercari home feed. Returns Mercari's own curated home-feed recommendations: listing summaries (title, price, thumbnail, condition, seller).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does disclose the return payload (title, price, thumbnail, condition, seller) and that results are curated rather than query-driven. However, it omits pagination behavior, result count, and whether the feed is personalized or geo-dependent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with the purpose front-loaded and the return-shape detail following. No filler, though the second sentence is a compact field list rather than a tighter phrase.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter feed tool with no output schema, the description supplies the essential missing piece: what a returned item looks like. Only pagination/volume limits are unstated, which is a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so per the baseline the schema fully covers the (empty) input surface and the description has nothing extra to document. No parameter ambiguity exists.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('Mercari home feed'), then clarifies the content is Mercari's own curated recommendations rather than a search result. This implicitly distinguishes it from siblings like mercari_search and mercari_item, though it never names them explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: an agent can infer this is the default/curated browse endpoint with no inputs. There is no statement of when to prefer it over mercari_search or mercari_master, and no exclusions or prerequisites are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.