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. 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	recent
`limit`	No	Number of posts to return (max 50)
`offset`	No	Pagination offset
`favorites_only`	No	Only return posts marked as favorite

TDQS

A4.1/5.0

Behavior4/5

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

Adds behavior beyond annotations: default sort order ('sorted by most recent by default') and the definition of 'viral' as beating the account baseline. The readOnlyHint annotation already covers the non-mutating profile, and the description is consistent with it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences with no filler; the core purpose is front-loaded and follow-up usage is tucked into the final sentences. The workflow guidance about url and preview/analysis is arguably extra, but it earns its place by reducing downstream agent decisions.

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?

With no output schema, the description compensates by noting that each post returns a url and that post ids feed into get_post_analysis. It misses an explicit statement of the return shape, but the invocation path is fully covered by the schema and annotations.

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 sort, limit, offset, and favorites_only. The description only reaffirms the default sort and adds no new parameter-level meaning.

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?

Description uses a specific verb and resource: 'List the viral posts detected on the user's watchlist' and defines the domain precisely as Instagram Reels and TikTok videos beating the account's baseline. This scope, plus watchlist framing, distinguishes it from nearby siblings like list_analyzed_posts and list_my_account_posts.

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?

Provides clear follow-up guidance: include each post's url and use get_post_preview for thumbnails and get_post_analysis for AI breakdowns. It does not explicitly state when to prefer this tool over list_analyzed_posts, but the 'viral' and 'watchlist' context makes the intended use clear.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Each tool has a distinct target resource/action, and the descriptions are unusually explicit about differences (e.g., 'Distinct from the watchlist', 'Separate list from list_tags'). A few pairs are still easy to confuse without careful reading: delete_folder vs delete_folders differ only by singular/plural, and the three download-URL tools (get_post_download_url, get_asset_download_url, get_my_account_post_download_url) plus the category/tag families require attention to pick correctly.

Naming Consistency4/5

The snake_case verb_noun pattern is followed consistently throughout (list_*, get_*, create_*, update_*, delete_*, set_*, tag_*). Minor deviations: archive_folder and archive_my_accounts also perform restore despite their names, delete_folder/delete_folders split one operation by cardinality, and tag_posts/tag_my_account use a different verb style than the set_* family for metadata mutations.

Tool Count2/5

At 56 tools, this far exceeds the 25+ threshold for 'too many,' even though the server spans multiple subdomains (watchlist, analysis, assignments, folders, my accounts, assets, Drive, categories/tags). Obvious consolidation candidates exist — delete_folder/delete_folders, the three download-URL getters, and the parallel list_my_account_* listers — and the sheer surface is heavy for an agent to navigate.

Completeness4/5

Core workflows are thoroughly covered with no dead ends: watchlist → analyze → assign → folder → track → approve has full lifecycle support, including reversible archive vs permanent delete choices. Minor gaps exist but are work-aroundable: no create/update for my accounts or models (app-side OAuth/admin only), no way to delete a viral post or a post note, and asset upload only happens in the app.

Resources

Need Help?