Jiji MCP

jiji_saved_listings

Read-onlyIdempotent

Retrieve your saved Jiji listings as read-only data, requiring Jiji sign-in and leaving your favourites unchanged.

Instructions

Read your saved listings from Jiji without changing favourites. Requires Jiji sign-in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jiji_saved_listings"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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 readOnly, idempotent, and non-destructive, so 'without changing favourites' largely restates them. However, the description adds one genuinely new behavioral fact beyond the annotations: the operation requires an authenticated Jiji session, which is important for calling it correctly.

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 short sentences with zero filler; the read-only guarantee is front-loaded and the prerequisite follows immediately.

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?

With an output schema present and pagination apparently handled by the jiji_next_page sibling, the description covers what an agent needs: purpose, safety, and the sign-in prerequisite. A brief note on empty results or account scoping would fully close it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter claims are made that could mislead.

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?

States a specific verb and resource: read saved listings from Jiji. No sibling covers saved listings (siblings cover search, details, conversations, etc.), so the tool is implicitly distinct, though the description never explicitly contrasts with an alternative.

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

Usage Guidelines3/5

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

The prerequisite 'Requires Jiji sign-in' and the hint to use jiji_open_sign_in-adjacent flows give usable context, but there is no explicit when-to-use vs. when-not guidance or named alternative (e.g., jiji_search for finding new listings).

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