Rolli MCP

list_keyword_searches

List paginated keyword searches and filter by status to track pending, started, finished, or failed searches.

Instructions

List all keyword searches. Returns a paginated list filtered by status.

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

Input Schema

Name	Required	Description	Default
`page`	No	Page number (100 results per page)
`show`	No	Filter by status (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.5.0Nov 4, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```
First observedv1.1.7Mar 18, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose two useful behavioral facts — results are paginated and can be filtered by status — but says nothing about permissions, result ordering, or what a page contains, which matters for a list tool with no output schema.

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 core purpose front-loaded before the return-behavior note. Nothing in it is wasted, even though the second sentence lightly overlaps the schema.

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?

For a zero-required-parameter list tool with a fully documented schema, the description is minimally sufficient. However, with no output schema it does not describe what a result entry looks like, and it gives no way to distinguish this tool from the other list_* siblings.

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 100%, including an enum for the status filter, so the baseline is 3. The description restates pagination and status filtering but adds no semantics beyond the schema (e.g. page-size implications or status lifecycle meaning).

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 uses a specific verb and resource ('List all keyword searches'), so an agent knows it enumerates keyword-search entities rather than executing one. It does not distinguish itself from the sibling list tools (list_expert_searches, list_user_searches), leaving the agent to infer the resource distinction from the name alone.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no reference to alternatives such as get_keyword_search or the sibling list tools. The agent must infer that this is the enumeration counterpart to keyword_search/get_keyword_search from naming conventions only.

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