Skip to main content
Glama
rolliinc

Rolli MCP

by rolliinc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

start_agent_run

Launch a social media investigation from a plain-English question. The agent searches Rolli IQ across platforms, analyzes posts, and returns a markdown report with evidence and confidence ratings.

Instructions

Start a Rolli Agent investigation. Submit a plain-English question; the agent plans a search strategy, queries Rolli IQ across platforms, analyzes posts, and produces a markdown intelligence report with signals, evidence links, and a confidence rating. Fails immediately (before starting) if the IQ credit balance is insufficient. Polls inline for up to 2 minutes. If the run finishes in that window, returns the full results; otherwise returns the run ID and a note to fetch the results with get_agent_run (typical run takes 3–5 minutes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoInvestigation mode (default: trend_briefing)
max_postNoMaximum posts per platform (default: 100)
metadataNoArbitrary JSON object stored on the run for your own tracking
questionYesPlain-English question (e.g., "What is being said about Tesla battery recalls this week?")
platformsNoPlatforms to search
time_windowNoTime window to search (default: 7d). Examples: 24h, 7d, 30d
parent_run_idNoUUID of a parent run (for follow-ups)
available_creditsNoReasoning effort: 1=low, 2=medium, 3=high, 4=max (default). Higher values let the agent perform more searches at higher cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • changedInput schema / properties / available_credits / description
      Previous value: -"Reasoning effort: 1=low, 2=medium (default), 3=high, 4=max. Higher values let the agent perform more searches at higher cost."New value: +"Reasoning effort: 1=low, 2=medium, 3=high, 4=max (default). Higher values let the agent perform more searches at higher cost."
    • changedInput schema / properties / max_post / description
      Previous value: -"Maximum posts per platform (default: 50)"New value: +"Maximum posts per platform (default: 100)"
  2. Changed1 schema field changedv1.4.0
    • changedInput schema / properties / platforms / items / enum
      Previous value: -[
-  "twitter",
-  "reddit",
-  "bluesky",
-  "youtube",
-  "threads",
-  "facebook",
-  "weibo"
-]New value: +[
+  "twitter",
+  "reddit",
+  "bluesky",
+  "youtube",
+  "threads",
+  "facebook"
+]
  3. Addedv1.3.0

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden. It explicitly discloses asynchronous execution, inline polling up to 2 minutes, the eventual run-ID fallback, typical 3-5 minute duration, and immediate failure on insufficient IQ credits. This is highly transparent for a side-effecting, asynchronous tool.

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?

The description is dense and efficient, with no filler. It front-loads the tool's purpose, then covers the behavioral contract: failure mode, polling window, and result handling. Every sentence earns its place.

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?

Despite having no output schema, the description fully covers the expected response shapes: a full markdown report when the run finishes or a run ID plus fetch instruction when it does not. For a complex, asynchronous, 8-parameter tool, this is enough for an agent to invoke and handle the result 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%, so the schema already documents every 8 parameters. The description adds general context around the 'question' parameter, but it does not materially extend the parameter semantics beyond what the input schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource, 'Start a Rolli Agent investigation,' and clearly explains the full workflow: planning a search strategy, querying across platforms, analyzing posts, and producing a markdown report. This distinct 'investigation' framing separates it from the sibling search/run-management tools.

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 provides clear context for when to use the tool: submit a plain-English question for an agent-driven investigation, and if the run exceeds the 2-minute polling window, fetch results with get_agent_run. It does not explicitly call out when not to use this tool in favor of keyword_search, user_search, or expert_search, so it falls just short of a fully explicit usage guideline.

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

Deploy Server

Other Tools