Rolli MCP

list_user_searches

Retrieve a paginated list of user searches and filter by status to review started, finished, pending, or failed search activity.

Instructions

List all user 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_user_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

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses only that results are paginated and filtered by status, which mostly restates the schema; it says nothing about permissions, default ordering, what fields each search record contains, or behavior when the status filter matches nothing.

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?

Two short, front-loaded sentences with no filler. The second sentence adds pagination and filtering information, though it is somewhat redundant against the schema and could have spent that space on sibling differentiation instead.

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 simple zero-required-parameter list tool with no output schema, the description covers the basics of pagination and filtering. The notable gap is disambiguation from the four-plus sibling list/lookup tools in this namespace, which an agent needs in order to select correctly.

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%, with both `page` (100 results per page) and `show` (status enum with default) fully documented in the schema. The description's phrase "filtered by status" merely echoes the `show` enum, so a baseline 3 is appropriate.

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 gives a clear verb+resource ("List all user searches"), so an agent immediately knows the operation and the entity. However, it never distinguishes this tool from sibling list tools such as list_expert_searches, list_keyword_searches, or get_user_search, so the agent must infer the difference 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 when-to-use guidance, no stated prerequisites, and no mention of when to prefer a sibling such as get_user_search or list_keyword_searches. The only contextual cue is the implicit "list" semantics, which the agent could already derive from the tool name.

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