XCut AI – Viral Content Research

Search the viral library

xcut_search_viral

Idempotent

Use this when the user asks what is going viral, trending or performing right now on Instagram, TikTok, YouTube or Facebook for a topic or niche, what a creator posts that works, or what ads run in the Meta Ad Library. mode is keyword (a topic) or profile (an account). Returns posts with views, engagement, links and captions, plus next_cursor for more. A fraction of a credit per page (cached pages free). Do not use for general web or news search, or for one profile's outliers versus its own normal (use xcut_find_outliers).

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": {
      "platform": "<platform>",
      "query": "<query>"
    },
    "name": "xcut_search_viral"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	keyword to search a topic (e.g. "meal prep"), or profile to see an account's top posts (query = @handle). Default keyword. Facebook supports profile only.	keyword
`limit`	No	Posts per page, 1-30. Default 15.
`query`	Yes	A topic, or a handle when mode is profile.
`cursor`	No	next_cursor from the previous page.
`platform`	Yes	instagram, tiktok, youtube, facebook, or meta_ads for the Meta Ad Library.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / mode / description

Previous value: -"keyword to search a topic (e.g. \"meal prep\"), or profile to see an account's top posts (query = @handle). Default keyword."New value: +"keyword to search a topic (e.g. \"meal prep\"), or profile to see an account's top posts (query = @handle). Default keyword. Facebook supports profile only."

First observedOct 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes beyond annotations by disclosing return contents (views, engagement, links, captions), pagination via next_cursor, and cost behavior ('a fraction of a credit per page, cached pages free'), which usefully explains why readOnlyHint is false (cache writes). It does not cover auth requirements or rate limits, so it falls short of 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.

Conciseness4/5

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

Front-loads the use case, then mode, then returns, then cost, then exclusions – a sensible priority order with no wasted sentences. Slightly dense, and the inline platform enumeration ('Instagram, TikTok, YouTube or Facebook') duplicates the platform enum, costing a perfect score.

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?

No output schema exists, and the description compensates by naming the returned fields and the pagination cursor. Combined with the explicit exclusions and cost note, an agent has everything needed to select and invoke 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 coverage is 100%, so the schema already documents every parameter including the mode enum semantics and the Facebook profile-only constraint. The description's mode sentence largely restates the schema, adding no syntax or format detail beyond it; baseline 3 applies.

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?

States a specific retrieval action (find what's going viral/trending/performing) across named platforms and both operating modes (keyword vs profile), and explicitly names the sibling it is not (xcut_find_outliers). An agent can distinguish it from xcut_get_breakouts or xcut_check_niche from the description alone.

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

Usage Guidelines5/5

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

Gives explicit trigger scenarios ('when the user asks what is going viral... what a creator posts that works, or what ads run in the Meta Ad Library') and explicit exclusions ('do not use for general web or news search, or for one profile's outliers versus its own normal') with the correct alternative named. Nothing is left to inference.

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

All XCut AI – Viral Content Research 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?