Rolli MCP

list_expert_searches

Retrieve a paginated list of expert searches and filter results by status to monitor running, completed, or failed searches.

Instructions

List all expert 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_expert_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
```
Addedv1.3.0Jun 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only states that results are paginated and status-filterable - both of which the schema already declares. It says nothing about ordering, what fields an expert search carries, or whether results are scoped to the caller's account.

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 sentences, front-loaded with the action, with no filler. The second sentence partially restates what the schema already conveys (pagination and status filtering), which is the only wasted effort.

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 two-optional-parameter read tool with no output schema, the description covers the essentials but leaves the concept of an "expert search" undefined and says nothing about result ordering or default behavior when no filter is given. It is adequate to call the tool, not complete.

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%: the schema documents the page parameter (100 results per page) and the show enum with a default of "all". The description adds no syntax or semantics beyond that, so the baseline of 3 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?

"List all expert searches" names a specific verb and resource, and the second sentence clarifies the scope (paginated, status-filterable). It stops short of distinguishing this from the many sibling list tools (list_keyword_searches, list_user_searches, list_agent_runs), so an agent must infer the difference from the noun 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?

The description gives no when-to-use guidance, no exclusion of alternatives, and no prerequisites. With five sibling list/search tools present, it never says whether to call this versus get_expert_search for a single item or list_keyword_searches for a different resource type.

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