Jiji MCP

jiji_next_page

Read-onlyIdempotent

Follow a search cursor to retrieve remaining items from the current Jiji page and automatically continue to the next-page URL, ensuring no results are omitted by a small limit.

Instructions

Follow a search cursor in this connection. Returns remaining items from the current Jiji page first, then follows Jiji's next-page URL; no results are omitted by a small limit. Cursors expire after 15 minutes.

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": {
      "cursor": "<cursor>"
    },
    "name": "jiji_next_page"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Oct 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent and openWorld, yet the description still adds real behavioral context: results are drained from the current page before the next-page URL, a small limit does not silently drop results, and cursors expire in 15 minutes. That expiry and ordering detail is exactly the kind of thing annotations cannot express.

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 short sentences, all load-bearing, with the core action front-loaded in the first sentence. Minor slack from the slightly vague phrase 'in this connection'.

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 ordering, pagination continuation and cursor expiry. The one real gap is not telling the agent where a cursor comes from, which matters for a continuation-only tool.

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 carry the params. It explains cursor semantics (search cursor, 15-minute lifetime) and clarifies that a small limit does not omit results, but never says what limit actually controls (page size) or mentions its 1-20 range/default of 8.

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?

Specific verb ('follow a search cursor') plus the pagination behavior it performs, which clearly separates it from jiji_search (which presumably issues the cursor). It never names jiji_search or any sibling explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied by 'Follow a search cursor' and the note that cursors expire after 15 minutes, telling the agent this is a continuation call that must be made promptly. There is no explicit statement of when to use it versus calling jiji_search again, nor how to obtain a cursor in the first place.

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