Rolli MCP

get_user_search

Retrieve profile details, metrics, and content analysis for a user search by ID; retry when results are pending and page oversized post lists separately.

Instructions

Get results for a user search by ID. Returns profile info, metrics, and content analysis. Oversized responses are truncated (truncated: true) — read the complete post list in pages with get_user_search_posts (offset, limit, fields=lean). results_pending: true means the search succeeded but the backend is still writing results; retry in a few seconds.

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": {
      "id": "<id>"
    },
    "name": "get_user_search"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	User search ID

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 / id / maximum
```
Added value: +9007199254740991
```
First observedv1.1.7Mar 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return payload (profile info, metrics, content analysis), the truncation behavior with its 'truncated: true' marker, and the asynchronous 'results_pending: true' state with retry guidance. It omits any permission or rate-limit context, which keeps it from a 5.

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 tight sentences, front-loaded with purpose, followed by return contents and then the two edge-case behaviors (truncation, pending results). Every sentence carries operational information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain return values and it does, including the sentinel fields an agent would otherwise misread. Retry and pagination escape hatches are both supplied, which is everything needed to call this 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% and there is only one parameter (id), which the schema already documents as 'User search ID'. The description's offset/limit/fields mentions describe the sibling tool's parameters, not this tool's, so no extra meaning is added for this schema. Baseline 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?

The description uses a specific verb and resource ('Get results for a user search by ID') and explicitly names the sibling get_user_search_posts as the route for the complete post list, so the agent can separate the two. It stops short of distinguishing this tool from user_search or list_user_searches, which sit in the same family.

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

Usage Guidelines4/5

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

It gives concrete when-to-use guidance for the alternative path: if the response is truncated, page through posts with get_user_search_posts (offset, limit, fields=lean). It also tells the agent what to do on results_pending (retry in a few seconds). It does not cover when to call user_search versus this retrieval tool.

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