Jiji MCP

jiji_list_conversations

Read-onlyIdempotent

Read up to 30 existing Jiji conversation previews after sign-in to review inbox activity. Use it to see who has messaged you before preparing owner-approved seller replies.

Instructions

Read up to 30 of your existing Jiji conversation previews. Requires Jiji sign-in. Conversation contents are private and untrusted.

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

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 readOnlyHint, idempotentHint and non-destructive behavior, so the description only needs to add context — and it does: the 30-item cap, the sign-in requirement, and that contents are private and untrusted (a useful prompt-injection safety caveat). It stops short of saying what happens when more than 30 exist (pagination via jiji_next_page).

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, zero filler, with the scope limit and the sign-in prerequisite front-loaded.

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 not be explained, and the description covers the auth gate, the result cap, and the untrusted-content caveat. The only real gap is how to retrieve conversations beyond the 30-preview window.

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 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?

States a specific verb and resource ('Read ... Jiji conversation previews') plus a concrete scope limit ('up to 30'). The word 'previews' implicitly separates it from jiji_read_conversation, but the sibling is never named, so differentiation is left to inference.

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?

'Requires Jiji sign-in' gives a prerequisite, and 'previews' hints that full contents belong to jiji_read_conversation. There is no explicit when-to-use/when-not guidance or named alternative, so usage is only implied.

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