Skip to main content
Glama
furima-mcp
by fxia0018

search_listings

Read-only

Search live listings across Japanese marketplaces with filters for site, price, and excluded keywords, returning merged results and per-site totals.

Instructions

Search listings that are for sale now on Japanese marketplaces.

Returns the merged listings (site, title, price in JPY, url, image, and for auctions the current bid count and end time), the total matches each site reports, and any site that failed.

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": {
      "query": "<query>"
    },
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder of results. price_* sorts across all sites.relevance
queryYesSearch keyword, ideally in Japanese.
sitesNoSites to search. Default: all that support the operation.
excludeNoDrop listings whose title contains any of these words (case-insensitive).
max_priceNoMaximum price in JPY.
min_priceNoMinimum price in JPY.
limit_per_siteNo
match_all_wordsNoKeep only listings whose title contains every word of the query (ignoring width, case, spaces and hyphens). The sites' own search is fuzzy: 'PS5 CFI-2000' also returns PS5 games.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint. The description adds valuable context about returned data (merged listings with site, title, price in JPY, url, image, auction bid count, end time, per-site totals, and failed sites), which goes beyond the annotations. It doesn't cover rate limits or authentication, but for a read-only search tool this is good.

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, front-loaded with purpose and then return values. No wasted words, and the structure is easy to parse.

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 an 8-parameter search tool with no output schema, the description covers the purpose and return structure well. The schema handles most parameter details. The main gap is usage guidance relative to siblings, which keeps it from a 5.

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 88%, so parameters are already well documented in the schema. The description does not add any parameter-level meaning beyond what the schema provides. The baseline score 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 verb 'Search' and resource 'listings' with the scope 'for sale now on Japanese marketplaces.' It does not distinguish from siblings like check_price or get_listing, but the purpose itself is unambiguous.

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?

No when-to-use or when-not-to-use guidance is provided. The description doesn't mention alternatives such as get_listing for details or sold_price_stats for historical prices. The implied usage is searching current listings, but no explicit routing is given.

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