Rolli MCP

list_agent_runs

Retrieve a paginated summary of Rolli Agent runs for AI-driven social intelligence investigations, excluding discarded runs and optionally filtering by status or user.

Instructions

List Rolli Agent runs (AI-driven social intelligence investigations). Returns a paginated summary list. Discarded runs are excluded.

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

Input Schema

Name	Required	Description
`limit`	No	Page size (default: 50, max: 100)
`offset`	No	Pagination offset (default: 0)
`status`	No	Filter by status
`user_id`	No	Filter to a specific Rolli user

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 / offset / maximum
```
Added value: +9007199254740991
```
Addedv1.3.0Jun 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful behaviors: results are paginated and only a summary representation is returned, and discarded runs are filtered out. It says nothing about ordering, total-count metadata, permissions, or rate limits, which leaves meaningful gaps for an unannotated read tool, but the exclusion rule is genuine behavioral detail.

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?

Three short sentences, front-loaded with the action and resource, then the return shape, then the exclusion rule. Nothing is redundant and nothing is buried.

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?

For a four-parameter, all-optional listing tool with no output schema, the description is nearly sufficient: it establishes scope, return shape, and one filtering rule. The remaining gap is that it does not describe what fields the summary entries contain or whether pagination metadata is returned, which matters slightly more without an output schema.

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 defaults, bounds, and an enum for status, so the schema already does the parameter work and baseline is 3. The description adds no filtering syntax or guidance beyond the note that discarded runs are excluded, which is tangentially relevant to the status filter but not explanatory.

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 ("List Rolli Agent runs") and glosses what an agent run is ("AI-driven social intelligence investigations"), which is real disambiguation value. It also marks the result shape ("paginated summary list"). It stops short of naming the sibling it contrasts with, notably get_agent_run for a single run or list_agent_schedule_runs for the scheduled variant, so 4 rather than 5.

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 the purpose and by the word "summary" (this is the browse/overview entry point, get_agent_run would be the detail path), but that inference is never made explicit. No when-not conditions or prerequisites are stated, and the sibling tools list includes several similarly named listing tools the agent must distinguish on its own.

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