Skip to main content
Glama

Tools

Tool

Beschreibung

list_keyword_searches

Listet alle Stichwortsuchen auf, gefiltert nach Status

keyword_search

Erstellt eine Stichwort-/Hashtag-Suche und gibt Ergebnisse bei Abschluss zurück

get_keyword_search

Ruft Stichwort-Suchergebnisse ab (Status, Analysen, Beiträge)

list_user_searches

Listet alle Benutzersuchen auf, gefiltert nach Status

user_search

Erstellt eine Benutzerprofilsuche und gibt Ergebnisse bei Abschluss zurück

get_user_search

Ruft Benutzersuchergebnisse ab (Profil, Metriken, Inhaltsanalyse)

get_topic_tree

Ruft den Themenbaum für eine Stichwortsuche ab

get_keyword_search_posts

Ruft Rohbeiträge aus einer Stichwortsuche ab

get_user_search_posts

Ruft Rohbeiträge aus einer Benutzersuche ab

get_integration_setup

Ruft aktuelle Integrationseinstellungen ab (Webhook-URL, Name)

update_integration_setup

Legt die Webhook-URL für Benachrichtigungen bei Suchabschluss fest

get_usage

Ruft API-Nutzungsdaten und Aufschlüsselungen pro Benutzer ab

Related MCP server: Grok X Insights MCP Server

Einrichtung

Sie benötigen ein Rolli-Konto mit API-Zugriff. Holen Sie sich Ihren API-Token von rolli.ai.

Claude Desktop / Claude Code / VS Code / Cursor / Windsurf

Fügen Sie dies zu Ihrer MCP-Konfiguration hinzu (claude_desktop_config.json, .vscode/mcp.json oder gleichwertig):

{
  "mcpServers": {
    "rolli": {
      "command": "npx",
      "args": ["-y", "@rolli/mcp"],
      "env": {
        "ROLLI_API_TOKEN": "your_token"
      }
    }
  }
}

ROLLI_USER_ID ist optional und standardmäßig auf "rolli-mcp" gesetzt. Legen Sie sie fest, um sie mit Ihrer eigenen Benutzer-ID zu überschreiben.

Optionale Umgebungsvariablen

Variable

Standard

Beschreibung

ROLLI_USER_ID

"rolli-mcp"

Benutzer-ID, die mit API-Anfragen gesendet wird

ROLLI_POLL_INTERVAL_MS

5000

Abfrageintervall (ms) beim Warten auf Suchergebnisse

ROLLI_MAX_POLL_MS

600000

Maximale Wartezeit (ms) vor Such-Timeout (Standard: 10 Min.)

Smithery

Dieser Server enthält eine smithery.yaml für die Bereitstellung über Smithery. Sie werden während der Einrichtung nach Ihrem API-Token gefragt.

Nutzungsbeispiele

Suche nach einem Stichwort in sozialen Medien:

"Suche nach Beiträgen über 'künstliche Intelligenz' auf Twitter und Reddit aus der letzten Woche"

Analyse eines Benutzerprofils:

"Suche nach @elonmusk auf Twitter und analysiere deren aktuelle Beiträge"

Themenaufschlüsselung abrufen:

"Zeige mir den Themenbaum für meine Stichwortsuche #123"

API-Nutzung prüfen:

"Wie viele Suchen habe ich diesen Monat verwendet?"

Webhook einrichten:

"Setze meine Webhook-URL auf https://myapp.com/rolli-callback"

Entwicklung

npm ci
npm run lint    # ESLint
npm run build   # TypeScript
npm test        # Vitest

CI läuft bei jedem Push und PR auf master. Releases, die auf GitHub veröffentlicht werden, werden automatisch auf npm veröffentlicht (erfordert NPM_TOKEN Repo-Geheimnis).

Lizenz

MIT

Available Tools

30 tools
cancel_agent_runA

Cancel a pending or running Rolli Agent run. Marks the run as failed.

Inputs: id (required).

create_agent_scheduleB

Create a recurring Rolli Agent report that runs on a cron-like cadence (daily, weekly, monthly, or one-time) with optional email and Slack notifications.

Inputs: name (required), question (required), starts_at (required), recurrence_time (required), +16 more.

delete_agent_runA

Soft-delete a Rolli Agent run. The record remains in the database for audit purposes but is hidden from listings. Only works on completed or failed runs — cancel the run first if it is still running.

Inputs: id (required).

delete_agent_scheduleA

Permanently delete a Rolli Agent schedule and its execution history. This is irreversible. Use pause_agent_schedule to temporarily stop a schedule without losing history.

Inputs: id (required).

get_agent_runA

Get a Rolli Agent run by ID. While running, returns progress (percentage, phase, current tool). Once complete, returns the full markdown report, signals, evidence links, and usage metrics.

Inputs: id (required).

get_agent_scheduleA

Get a Rolli Agent schedule's full configuration plus its 10 most recent execution records.

Inputs: id (required).

get_integration_setupA

Get the current integration settings (webhook return URL and integration name).

Inputs: no named parameters.

get_keyword_search_postsA

Get raw posts from a keyword search. The first line says how many of the search's posts this response shows and the offset of the next page; total, returned, offset and platform_counts (posts per platform across the whole search) are in the JSON. Read a large search in pages with offset and limit, one platform at a time, and fields=lean when the text matters more than media and profile URLs. A response over the size cap is marked truncated: true.

Inputs: search_id (required), limit, fields, offset, +1 more.

get_topic_treeB

Get the conversation topic tree for a keyword search. Shows how topics and subtopics are distributed across the search results.

Inputs: search_id (required), platform.

get_usageA

Get API usage data. Returns search counts, per-user breakdowns, and the current IQ credit balance (credits.credits_remaining, credits.credits_limit, credits.period_reset_date — the latter two are null for one-time credit grants). Optionally filter by month.

Inputs: month.

get_user_search_postsA

Get raw posts from a user search. The first line says how many of the profile's posts this response shows and the offset of the next page; total, returned and offset are in the JSON. Read a large search in pages with offset and limit, and fields=lean when the text matters more than media and profile URLs. A response over the size cap is marked truncated: true.

Inputs: search_id (required), limit, fields, offset.

list_agent_runsA

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

Inputs: limit, offset, status, user_id.

list_agent_schedule_runsA

List the full execution history of a Rolli Agent schedule, including a preview of each linked agent run.

Inputs: id (required), limit, offset.

list_agent_schedulesB

List Rolli Agent scheduled reports. Schedules execute on a daily/weekly/monthly/once cadence and produce a new agent run each time.

Inputs: limit, offset.

list_expert_searchesC

List all expert searches. Returns a paginated list filtered by status.

Inputs: page, show.

list_keyword_searchesB

List all keyword searches. Returns a paginated list filtered by status.

Inputs: page, show.

list_user_searchesC

List all user searches. Returns a paginated list filtered by status.

Inputs: page, show.

pause_agent_scheduleA

Pause a Rolli Agent schedule so it stops executing. The schedule and its history are preserved — resume it later with resume_agent_schedule.

Inputs: id (required).

rerun_agent_runA

Rerun a failed, waiting, or stuck Rolli Agent run. Resets the run to pending and re-enqueues it. Running runs are force-cancelled first. Returns 422 if the run is already completed. Fails immediately if the IQ credit balance is exhausted (a rerun needs at least 1 credit).

Inputs: id (required).

resume_agent_scheduleA

Resume a paused Rolli Agent schedule. next_run_at is recalculated based on the recurrence parameters.

Inputs: id (required).

start_agent_runA

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).

Inputs: question (required), mode, max_post, metadata, +4 more.

update_agent_runB

Update a Rolli Agent run's metadata (rename or pin). At least one of pinned or label is required.

Inputs: id (required), label, pinned.

update_agent_scheduleB

Partially update a Rolli Agent schedule. Unspecified fields are left unchanged. next_run_at is recalculated if any recurrence parameter changes.

Inputs: id (required), mode, name, ends_at, +14 more.

update_integration_setupC

Update integration configuration. Set the webhook URL that receives notifications when a search completes.

Inputs: return_url (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 30 tools

    Disambiguation4/5

    The three search creators (keyword_search, user_search, expert_search) target genuinely distinct resources, and the get_/list_/get_*_posts variants are separated by clear descriptions about paging and polling. The only friction is the large family of similarly named search readers (get_keyword_search vs. get_keyword_search_posts vs. list_keyword_searches), which an agent must read carefully but can still distinguish.

    Naming Consistency4/5

    Nearly everything follows snake_case verb_noun (get_agent_run, create_agent_schedule, cancel_agent_run, list_user_searches), and the agent/schedule families are very predictable. The deviations are the three creation tools named noun-first (keyword_search, user_search, expert_search) instead of create_*, which breaks the pattern in the single most-used operation.

    Tool Count3/5

    30 tools is heavy and crosses the point where surface area itself becomes a selection cost. The count is partly justified by four sub-domains (searches, agent runs, schedules, integrations/usage), but the search family alone spawns ~12 tools that could be consolidated with a resource parameter.

    Completeness4/5

    Agent runs and schedules have full lifecycle coverage (create/get/list/update/delete/cancel/rerun; create/get/update/delete/pause/resume/runs), and searches cover create/get/list/paged posts plus polling semantics. The gap is that no search type (keyword, user, expert) can be deleted or updated, and there is no way to re-fetch a stale search beyond retrying.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      SocialCrawl provides the "best" quality public web data on the internet. Access 65+ real-time social media, e-commerce and public web data from a single API with a single schema.
      5
      569 npm
      28
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, describe and call 239 social data endpoints across Instagram, TikTok, LinkedIn, Facebook, YouTube, X, Reddit, Threads and Pinterest through a single API key, covering profiles, posts, comments, followers, hashtags, ads and transcripts with one unified schema. Full responses are saved server-side and can be re-sliced for free with jq, fields or size outlines, so agents pull only the data they need into context.
      121 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI tools to read publicly visible social media posts, comments, profiles, and trends from 18 platforms such as TikTok, Instagram, X, Reddit, YouTube, Xiaohongshu, and Weibo, on a prepaid pay-per-call basis where failed calls are free. Ships tools for search, trending, detail, comments, user profiles and posts, plus higher-level workflows like brand buzz, comment analysis, account watching, creator discovery, bulk link data, and viral finding.
      MIT