Jiji MCP

jiji_search

Read-onlyIdempotent

Search Jiji marketplace listings by query using category, region, price, and exact attribute filters, and paginate with returned cursors.

Instructions

Search Jiji listings with native category/region/price and attribute filters. For condition, brand or type, read jiji_account_data listing_filters for the category slug, set category_slug, and pass its exact filter_name/value in filters (a string, or an array for multiple selections). Do not guess attribute IDs or replace condition filters with query words. Follow returned cursor, never invent pagination URLs.

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_search"
  }
}

Input Schema

Name	Required	Default
`sort`	No	rel
`limit`	No
`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.9/5.0

Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, open-world tool. The description adds useful behavioral constraints beyond annotations: do not guess attribute IDs, do not replace condition filters with query words, and do not invent pagination URLs. It does not describe rate limits or other operational behavior, but the output schema covers return shape.

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 and front-loaded: the first sentence defines the scope, then it gives filter-specific and pagination-specific rules. Every sentence adds operational value, with no redundant restatement of the tool name or annotations.

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

Completeness3/5

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

This is a complex search tool with 10 parameters, nested filters, and no schema descriptions. The description covers the most error-prone areas, attribute filters and pagination, but it omits guidance on several other parameters and does not fully disambiguate ID versus slug parameters. The output schema reduces the need to describe return values.

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%, so the description must compensate for 10 parameters, including a nested filters object. It usefully explains filters (string or array, exact filter_name/value) and category_slug setup via jiji_account_data. However, it does not explain sort, limit, min_price/max_price, region_id vs region_slug, or category_id vs category_slug, leaving substantial semantic gaps.

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 clearly states a specific verb and resource: search Jiji listings with category/region/price and attribute filters. It distinguishes itself from jiji_account_data by directing the agent there for listing_filters rather than using this tool for that data. However, it does not explicitly contrast with sibling search/navigation tools such as jiji_compare_listings or jiji_next_page.

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 provides concrete usage guidance for attribute filters: read jiji_account_data listing_filters, set category_slug, and pass exact filter_name/value values. It also gives pagination guidance to follow returned cursors rather than inventing URLs. It lacks explicit when-not-to-use guidance versus other listing tools, so it is not fully exhaustive.

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