Skip to main content
Glama

Search viral videos

search_viral_videos
Read-only

Search viral short-form videos and posts across YouTube, Instagram, TikTok, X, Reddit, Threads, and LinkedIn (same engine as revid.ai/search). Semantic query plus filters on engagement (min likes/views/shares/comments), platform, language, hashtags, posting date, duration, and AI-analyzed style (mood, content type, perspective, shooting style, visual origin, brand promotion). Each result includes the post URL, a playable video URL when available, the full transcript, a content summary, engagement counts and rate, author info, and hashtags — useful for studying what works before creating content with render_video. Rate limited per plan (free keys get a small daily allowance); a RATE_LIMIT_EXCEEDED error says when the allowance resets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_viral_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNoMood filter.
sortNoResult order. Default: relevance.
limitNoResults to return (max 12 per call — backend hard cap).
queryNoFree-text semantic query, e.g. 'AI tools for founders'. Matches meaning, not just keywords.
settingNoWhere the video takes place.
hashtagsNoHashtags (without #) — results must include at least one.
languageNoISO language code filter, e.g. 'en'.
minLikesNoMinimum like count.
minViewsNoMinimum view count.
minSharesNoMinimum share count.
platformsNoPlatforms to search. Defaults to youtube, instagram, tiktok.
viralOnlyNoOnly posts in the 'high' or 'viral' engagement tier. TikTok has no tier data, so TikTok results need 100k+ likes instead.
contentTypeNoContent format filter.
maxDurationNoMaximum duration in seconds (TikTok results only). Default 900.
minCommentsNoMinimum comment count.
minDurationNoMinimum duration in seconds (TikTok results only).
perspectiveNoSubject perspective filter.
postedAfterNoOnly posts after this date (ISO date or unix seconds).
postedBeforeNoOnly posts before this date (ISO date or unix seconds).
visualOriginNoReal shot vs AI generated vs animation.
shootingStyleNoCamera/shooting style filter.
hasBrandPromotionNoFilter for videos with (true) or without (false) brand promotion.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
methodYes
statusYes
endpointYes
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so the bar is lower, yet the description still adds real context: per-plan rate limits, the RATE_LIMIT_EXCEEDED error and that it reports reset time. The result-field enumeration is somewhat redundant given an output schema exists, which keeps this from 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?

It is front-loaded: purpose first, then filter categories, then return contents, then rate-limit caveat. Four sentences for a 22-parameter tool is proportionate, though the long result-field list and the parenthetical engine URL are somewhat expendable.

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 22-parameter, open-world search tool it covers purpose, scope, defaults, and rate-limit behavior, and the output schema removes the need to explain return shapes. It omits that all parameters are optional and that no filters yield broad results, a minor gap given complexity.

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 all 22 parameters are already documented in the schema, including the TikTok-only duration caveat and the viralOnly tier fallback. The description only groups the filters into categories without adding per-parameter meaning, so the 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?

The opening sentence names a specific verb+resource (search viral short-form videos and posts), enumerates the seven platforms covered, and states the backing engine (revid.ai/search). It also distinguishes itself from a sibling by framing results as input to 'creating content with render_video'.

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 gives clear usage context — study what works before creating content — and names render_video as the downstream alternative. It does not state when NOT to use it (e.g., a non-viral or keyword-only search sibling), but the intended workflow is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources