Skip to main content
Glama
TikTok Intelligence MCP Server

TikTok Intelligence MCP Server

by willowswt

scan_breakout_tiktok_sounds

Read-onlyIdempotent

Discover trending and breakout TikTok sounds by niche keyword, returning sound IDs, titles, original/commercial flags, MP3 previews, velocity scores, and sample videos.

Instructions

Discover trending and breakout TikTok audio/music tracks in any niche (keyword), returning sound IDs, titles, original vs. commercial flags, MP3 preview URLs, velocity score, and viral sample videos.

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": {
      "keyword": "<keyword>"
    },
    "name": "scan_breakout_tiktok_sounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesNiche keyword (e.g. "gym motivation", "aesthetic vlog").
maxSoundsNoMaximum sound trends to return (1-15, default 6).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that by enumerating the returned payload (sound IDs, titles, original vs. commercial flags, MP3 preview URLs, velocity score, sample videos), which matters because no output schema exists. It omits rate limits, auth, or pagination behavior, keeping it below 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.

Conciseness5/5

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

A single front-loaded sentence with no filler. The long return-field list is justified because no output schema exists to convey that information elsewhere.

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 two-parameter read-only discovery tool with no output schema, the description covers purpose, input scope, and return shape adequately. It leaves undefined what 'velocity score' measures and what separates 'breakout' from merely 'trending', which is a modest gap.

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 both `keyword` and `maxSounds` are already documented with examples and a range. The description only echoes the keyword concept and adds no format or interpretation detail beyond the schema, matching the baseline for high-coverage schemas.

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?

The description uses a specific verb-plus-resource formulation ('Discover trending and breakout TikTok audio/music tracks') and scopes it by keyword, which makes it clearly distinct from the sibling tools covering creators, videos, sponsors, hooks, and comments. It does not name any sibling explicitly, so it stops short of a 5.

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?

Usage is only implied: 'in any niche (`keyword`)' tells the agent the input shape but gives no guidance on when to pick this over adjacent tools such as search_tiktok_videos or extract_viral_hooks_and_scripts. No exclusions, prerequisites, or conditions are stated.

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