Skip to main content
Glama
deenesjakoruzh
trendsmcp-ai

tiktok-trends-mcp

by trendsmcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tiktok-trends-mcp

TikTok Trends MCP 兼容 兼容 Claude 兼容 Cursor

TikTok 趋势数据，专为 AI 助手打造 在 TikTok 趋势成为主流之前发现它们。追踪话题标签的体量增长、病毒式爆发和平台特定的需求信号——这些都可以通过你的 AI 用自然语言获取。

完整文档和在线演示： https://trendsmcp.ai/tiktok-trends

属于 Trends MCP——该 MCP 服务器提供来自 12+ 数据源的实时趋势数据。 查看主仓库：https://github.com/trendsmcp/trends-mcp

两步快速开始

第 1 步： 在 trendsmcp.ai 免费获取你的 API 密钥 每天 100 次请求，无需信用卡。

第 2 步： 添加到你的 AI 客户端（替换 YOUR_API_KEY）：

+ 添加至 Cursor（一键安装）

Cursor / Windsurf / Cline   （~/.cursor/mcp.json 或等效路径）

{
  "mcpServers": {
    "trends-mcp": {
      "url": "https://api.trendsmcp.ai/mcp",
      "transport": "http",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

VS Code / GitHub Copilot   （.vscode/mcp.json）

{
  "servers": {
    "trends-mcp": {
      "type": "http",
      "url": "https://api.trendsmcp.ai/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Claude Desktop   （claude_desktop_config.json） 用户 → 设置 → 开发者 → 编辑配置 — 在 mcpServers 内添加

{
  "mcpServers": {
    "trends-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.trendsmcp.ai/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude.ai（浏览器）   设置 -> 连接器 -> 添加自定义连接器：

https://api.trendsmcp.ai/mcp

Related MCP server: tiktok-trends-mcp

示例查询

连接后，向你的 AI 提问：

get_trends(keyword='booktok', source='tiktok', data_mode='weekly')

可用工具

工具

功能说明

get_trends

获取该数据源上某个关键词的时间序列

get_growth

过去 1 周、1 个月、3 个月、6 个月、1 年的增长百分比

get_top_trends

当前该数据源上正在流行的趋势

get_ranked_trends

根据体量排名靠前的话题

常见问题

Trends MCP 提供哪些 TikTok 数据？

TikTok 话题标签趋势体量——归一化兴趣度、增长率和历史时间序列。这反映了某一话题标签在平台上的出现频率和随时间增长的情况。

我能多早发现 TikTok 趋势？

Trends MCP 提供周度和日度数据。日度数据（最近 30 天）能让你在话题标签达到主流饱和之前，发现早期的增长峰值。

我可以将 TikTok 趋势与 Google 搜索对比吗？

可以。用一个调用同时查询两个数据源。TikTok 通常在同一个话题在 Google 搜索上兴起前的 2-4 周就显示出峰值，因此跨平台比较可以作为一种领先指标策略。

该工具可用于 TikTok 上的品牌监测吗？

可以。追踪某个品牌名或产品话题标签随时间的变化，衡量该品牌在 TikTok 上相对于竞争对手的影响力增长。

TikTok 话题标签区分大小写吗？

不区分。查询在查找前会进行归一化处理。你可以使用 booktok、BookTok 或 #booktok——它们都会返回相同的信号。

所有数据源

Trends MCP 通过一个连接覆盖 12+ 个数据源： Google 搜索、YouTube、TikTok、Reddit、Amazon、Wikipedia、 新闻情感、网站流量、应用下载、Steam、npm 等。

浏览全部：https://trendsmcp.ai/data-sources

也可作为 Python 客户端使用

同一个 API 密钥可直接在 Python 中使用，无需 MCP 宿主。

pip install tiktok-trends-mcp
import os
from tiktok_trends_mcp import TrendsMcpClient, SOURCE

client = TrendsMcpClient(api_key=os.environ["TRENDSMCP_API_KEY"])

series  = client.get_trends(source=SOURCE, keyword="your keyword")
growth  = client.get_growth(source=SOURCE, keyword="your keyword", percent_growth=["1M", "3M", "12M"])
top     = client.get_top_trends(type="Tiktok", limit=10)

完整的 Python 文档：trendsmcp.ai/docs

许可证

MIT © Trends MCP

Available Tools

3 tools
get_growthA
Read-onlyIdempotent
Inspect

Point-to-point growth for a keyword on one or more sources. Each window is a preset string (12M, 3M, YTD, and the other listed periods). Values are on a 0-100 scale, plus absolute volume when available. Prefer this over get_time_series for growth questions. app downloads and app rankings are keyword sources (Android bundle ID). They are not the App Store / Google Play live boards on get_top_trends. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

ParametersJSON Schema
NameRequiredDescriptionDefault
sourceYesOne source, or comma-separated sources (e.g. 'amazon, tiktok, youtube'). Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm', 'python', 'steam', 'app downloads', 'app rankings'.
keywordYesWhat to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume): any name or phrase, e.g. 'nike'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART. If the request includes app downloads or app rankings with other sources, keyword must still be the Android bundle ID.
percent_growthNoGrowth windows. Default if omitted: ['12M']. Each item must be a preset string: '7D', '1W', '14D', '2W', '30D', '1M', '2M', '3M', '6M', '9M', '12M', '1Y', '18M', '24M', '2Y', '36M', '3Y', '48M', '4Y', '60M', '5Y', 'MTD', 'QTD', 'YTD'. Every preset is a two-date comparison.

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint, openWorldHint, and idempotentHint annotations, the description adds useful behavioral context: values are on a 0-100 scale with absolute volume when available, and the agent should tell the user their plan limit is reached on rate limiting or quota exhaustion. These details are not present in the structured fields and do not contradict the annotations.

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?

The description is compact and every sentence earns its place: core operation, output scale, sibling preference, app-source caveat, and rate-limit handling. It front-loads the primary purpose and avoids redundant phrasing.

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?

With a detailed input schema, an output schema, and safety annotations, the description fills the remaining gaps: tool selection, output scale, source disambiguation, and error behavior. It is complete enough for an agent to invoke the tool correctly without further inference.

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?

The input schema already documents all parameters thoroughly, including valid sources, keyword formatting rules per source, and every preset growth window. The description references preset windows and Android bundle IDs but does not add meaning beyond the schema, so a baseline of 3 is appropriate.

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 description opens with a specific action and resource: 'Point-to-point growth for a keyword on one or more sources.' It also names sibling tools to disambiguate itself, stating it is preferred over get_time_series for growth questions and clarifying that app sources are not the live boards on get_top_trends.

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?

It gives an explicit selection rule: 'Prefer this over get_time_series for growth questions.' It also warns against confusing app downloads/app rankings with get_top_trends live boards, and specifies how to handle rate limits or quota exhaustion. This gives the agent clear when-to-use and when-not-to-use guidance.

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

get_time_seriesA
Read-onlyIdempotent
Inspect

Full historical series for one keyword and one source (0-100 values, plus volume when available). Use for charting or custom math. Not for live 'what's trending now' boards (use get_top_trends). For most growth questions, use get_growth. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

ParametersJSON Schema
NameRequiredDescriptionDefault
sourceYesExactly one source per request. Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm', 'python', 'steam', 'app downloads', 'app rankings'.
keywordYesWhat to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume): any name or phrase, e.g. 'tesla'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART.

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and idempotentHint. The description adds behavioral context beyond those hints: the 0-100 value range, volume availability, and rate-limit/quota handling instructions. This provides useful operational detail that annotations do not convey, though the core safety profile is already covered by hints.

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?

Three sentences, each earning its place: purpose and scope, usage routing, and error handling. Front-loaded with the core purpose; no repetition or fluff. The alternative tool routing is included efficiently.

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?

Given a two-parameter tool with a full output schema, the description covers purpose, usage scenarios, alternatives, and error handling. An agent has all necessary information to decide when to call it and what to expect, with no critical gaps.

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% and both parameters have detailed, source-specific descriptions (e.g., keyword format per source, valid source list). The tool description adds no additional parameter meaning beyond restating 'one keyword and one source', so the baseline for full schema coverage 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 description explicitly states it returns 'Full historical series for one keyword and one source' with a value range and volume detail. It distinguishes itself from siblings get_top_trends and get_growth by stating what it is not for (live trending, growth questions), making the tool's purpose unambiguous.

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?

Directly states when to use it: 'Use for charting or custom math' and when not to: 'Not for live trending (use get_top_trends)' and 'For most growth questions, use get_growth'. Also provides explicit handling for rate-limited or quota-exhausted requests, which is actionable guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv0.1.0
    • First observedget_growth
    • First observedget_time_series
    • First observedget_top_trends
Deploy Server
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

TDQS

A4.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool addresses a distinct retrieval pattern: get_growth handles window-over-window comparisons for keyword sources, get_time_series provides full historical data for charting, and get_top_trends targets current live boards without a keyword. The descriptions explicitly cross-reference each other and state when one is preferred, so an agent should be able to select correctly.

Naming Consistency5/5

All three tool names follow the same get_ + noun pattern using snake_case, making the collection predictable. There are no mixed conventions or vague verbs.

Tool Count5/5

Three tools is well-scoped for a trends data server: one for growth comparisons, one for full history, and one for live top lists. Each tool provides a distinct high-level capability without redundancy or bloat.

Completeness4/5

The read-only trend surface is broadly covered: live boards, point-to-point growth, and historical series cover the main ways trends data would be requested. A minor gap is that there is no explicit discovery tool for available sources/categories, though the descriptions document them sufficiently for most workflows.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers