Skip to main content
Glama
TikTok Intelligence MCP Server

TikTok Intelligence MCP Server

by willowswt

extract_viral_hooks_and_scripts

Read-onlyIdempotent

Extracts timestamped TikTok hooks, body scripts, CTAs, speaking pace, and virality multipliers from videos by keyword or URL, so you can analyze what makes winning content work.

Instructions

Extract timestamped first-3-second spoken hooks, body scripts, closing CTAs, speaking pace (WPM), hook archetype, and outlier virality multiplier from TikTok videos matching keyword or a specific videoUrl.

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": "extract_viral_hooks_and_scripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordNoTikTok niche keyword (e.g. "marketing tips"). Optional if `videoUrl` is set.
videoUrlNoOptional direct TikTok video URL.
maxResultsNoMaximum analyzed videos to return (1-15, default 5).
hookWindowSecondsNoOpening hook window in seconds (default 3.5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds meaningful value by enumerating exactly what is returned: timestamped first-3-second hooks, body scripts, closing CTAs, WPM pace, hook archetype, and outlier virality multiplier. It does not mention cost, latency, or failure behavior for empty input, keeping it 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?

A single front-loaded sentence with no boilerplate; the enumerated output list is long but each item carries real information. Minor deduction for cramming six output types and two input modes into one clause-heavy sentence rather than structuring them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does well by naming the returned fields, which is the main completeness risk here. The gap is the zero-required-parameter design: it never states what the tool does if neither `keyword` nor `videoUrl` is provided, nor any limits on extraction depth.

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 all four parameters, making 3 the baseline. The description adds only mild context by tying `hookWindowSeconds` conceptually to "first-3-second hooks" (though the schema default is 3.5, a slight ambiguity) and by clarifying that keyword and videoUrl are alternative selectors.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb ("Extract") with a specific set of resources (timestamped hooks, body scripts, CTAs, WPM, hook archetype, virality multiplier) and a clear source (TikTok videos by keyword or URL). This is clearly distinguishable from siblings like find_tiktok_creator_emails or scan_breakout_tiktok_sounds, though it does not explicitly name an alternative.

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

Usage Guidelines3/5

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

The phrase "matching `keyword` or a specific `videoUrl`" implies the two selection modes, giving some usage context. However, there is no explicit guidance on when to prefer this over search_tiktok_videos, and no statement of what happens when neither selector is supplied even though both are optional.

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