Skip to main content
Glama
furima-mcp
by fxia0018

get_listing

Read-only

Retrieve full details for a Mercari, Yahoo! Auctions, Yahoo! Flea Market, or Rakuma listing from its URL, including price, status, condition, description, images, and seller.

Instructions

Full details of one listing: price, status, condition, description, images and seller.

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": {
      "url": "<url>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA Mercari, Yahoo! Auctions, Yahoo! Flea Market or Rakuma listing URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context by listing exactly which listing attributes are returned, but says nothing about behavior on unsupported URLs, rate limits, or partial data.

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?

A single sentence that front-loads the operation and then enumerates the returned fields. No wasted wording or redundant restatement of the name.

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?

For a simple one-parameter read tool with annotations and no output schema, the description is nearly complete: it conveys both purpose and the shape of the response. A minor gap is the absence of any note about invalid or unsupported URLs.

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 coverage is 100% and the url parameter already documents the accepted marketplaces (Mercari, Yahoo! Auctions, Yahoo! Flea Market, Rakuma). The description adds no further meaning about the URL beyond what the schema provides, so the baseline of 3 applies.

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?

The description states a specific resource ('one listing') and enumerates the returned fields (price, status, condition, description, images, seller), making the operation clear. It does not explicitly name or contrast with siblings like check_price or sold_price_stats, though 'one listing' implicitly distinguishes it from search_listings.

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?

There is no explicit when-to-use guidance and no mention of alternatives such as check_price for price-only lookups or sold_price_stats for aggregates. The agent must infer that this is the detail-fetch tool from the singular 'one listing' phrasing.

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