Jiji MCP

jiji_market_prices

Read-onlyIdempotent

Summarize advertised asking prices from one Jiji search page using category, region, price, and attribute filters; compare used and new asking prices separately, not completed sales or valuations.

Instructions

Summarize advertised asking prices from one search page, with native category/region/price/attribute filters. Learn exact condition filter_name/value from jiji_account_data listing_filters, then sample used and new separately. These are asking prices, not completed sales or a valuation.

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": "jiji_market_prices"
  }
}

Input Schema

Name	Required	Default
`sort`	No	rel
`query`	Yes
`filters`	No
`max_price`	No
`min_price`	No
`region_id`	No
`category_id`	No
`region_slug`	No
`category_slug`	No

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Oct 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, so the bar is lower. The description does add real context beyond them — that results cover only one search page and that prices are asking prices rather than sold prices — but it says nothing about result volume, sampling limits, or what happens when no matches exist.

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?

Three tight sentences with the core scope front-loaded and the caveat last, which is the right ordering. Slightly dense, but no sentence is filler.

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?

An output schema exists, so return values need no explanation, and the description covers the scope trap and the prerequisite lookup. Remaining gaps are the parameter-level details (sort semantics, slug vs id) that a 9-parameter tool arguably needs.

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% across 9 parameters, so the description carries the burden. It does map loosely onto filter families ('category/region/price/attribute', plus the condition filter key), but leaves the sort enum (rel/new/price/price_desc), the id-vs-slug choice for category and region, and the filter_ pattern syntax undocumented.

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 and resource — 'summarize advertised asking prices from one search page' — which is clearly distinguishable from listing-level siblings like jiji_search or jiji_listing_details. It scopes the result explicitly ('asking prices, not completed sales or a valuation'), though it never names jiji_search as the non-aggregating alternative.

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

Usage Guidelines4/5

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

It gives concrete usage direction: learn the exact condition filter_name/value from jiji_account_data listing_filters, then sample used and new separately. That is actionable guidance about the prerequisite step and how to segment a sample, but there is no explicit statement of when to prefer jiji_search instead or when this tool is inappropriate.

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