Viral Manager

list_viral_posts

Read-only

List the viral posts detected on the user's watchlist (Instagram Reels and TikTok videos that beat the account's baseline). Sorted by most recent by default. To poll for new detections, pass since (ISO date): posts detected after it are returned oldest-first; page with offset until count < limit, then keep the returned next_since for the next poll. When presenting posts to the user, always include each post's url link, and use get_post_preview to show the thumbnails of the highlighted ones inline. Use get_post_analysis with a post id to read the AI breakdown of a specific post.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	'recent' = newest first, 'score' = highest virality score first. Ignored when `since` is set.	recent
`limit`	No	Number of posts to return (max 50)
`since`	No	Only posts detected strictly after this ISO 8601 date (use the `next_since` of your previous poll)
`offset`	No	Pagination offset
`favorites_only`	No	Only return posts marked as favorite

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 22, 2026

addedInput schema / properties / since

Added value: +{
+  "description": "Only posts detected strictly after this ISO 8601 date (use the `next_since` of your previous poll)",
+  "format": "date-time",
+  "type": "string"
+}

changedInput schema / properties / sort / description

Previous value: -"'recent' = newest first, 'score' = highest virality score first"New value: +"'recent' = newest first, 'score' = highest virality score first. Ignored when `since` is set."

First observedSep 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavior beyond that: default sorting by recent, `since` overriding sort, oldest-first polling order, and the pagination stop condition. It does not describe the return shape, but for a read-only list tool the added behavioral detail is substantial.

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 but well-structured: it opens with purpose, then covers sorting, polling, pagination, and downstream tool usage. Every sentence carries operational value, and there is no filler or repetition of schema fields.

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 read-only tool with no required parameters, the description covers the core operational contract: sorting, paging, polling state, and required post-presentation behavior. The absence of an output schema leaves some return-shape ambiguity, but the description is unusually explicit about the polling contract and follow-up tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the polling workflow with `since`, `offset`, `count`, and `next_since`, and reinforces that `sort` is ignored when `since` is set. This goes beyond simply restating the schema parameters.

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 names a specific verb and resource: lists viral posts detected on the user's watchlist, and defines 'viral' as Instagram Reels and TikTok videos that beat the account's baseline. This clearly distinguishes it from generic list tools like list_analyzed_posts or list_watchlist_accounts.

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?

The description gives explicit usage scenarios: polling with `since`, paginating with `offset` until `count < limit`, persisting `next_since`, and routing to get_post_preview and get_post_analysis. It does not explicitly contrast this tool with sibling list tools, but the usage context is strong and actionable.

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

All Viral Manager tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?