Skip to main content
Glama
enesjakozh
Seym0n

TikTok MCP

by Seym0n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

TikTok MCP

图片（12）

TikTok MCP 通过 TikNeuron 将 TikTok 接入 Claude AI 和其他应用程序。这款 TikTok MCP 允许您

  • 分析TikTok视频以确定病毒式传播因素

  • 从 TikTok 视频中获取内容

  • 使用 TikTok 视频聊天

可用工具

tiktok_可用字幕

描述：
查找可用的字幕，即 TikTok 视频的内容。用于查找 TikTok 视频是否有可用的内容（字幕）。返回视频可用的字幕，字幕可以支持多种语言和格式，例如自动语音识别、机器翻译或创作者字幕等。

输入参数：

tiktok_get_subtitle

描述：
获取 TikTok 视频 URL 的字幕（内容）。用于获取 TikTok 视频的字幕、内容或上下文。如果未提供语言代码，该工具将返回自动语音识别的字幕。

输入参数：

tiktok_get_post_details

描述：
获取 TikTok 帖子详情。返回视频详情，例如：

  • 描述

  • 创建者用户名

  • 标签

  • 点赞、分享、评论、浏览和书签的数量

  • 创建日期

  • 视频时长

输入参数：

Related MCP server: tiktok-mcp

要求

对于此 TikTok MCP，您需要

设置

  1. 克隆存储库

git clone https://github.com/Seym0n/tiktok-mcp.git

  1. 安装依赖项

npm install

  1. 构建项目

npm run build

这将创建文件build\index.js

在 Claude AI 中使用

将以下条目添加到mcpServers ：

"tiktok-mcp": {
    "command": "node",
    "args": [
      "path\\build\\index.js"
    ],
    "env": {
      "TIKNEURON_MCP_API_KEY": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
    }
}

并将路径替换为 TikTok MCP 的path ，并使用 TIkNeuron API 密钥替换XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

因此mcpServers将如下所示：

{
  "mcpServers": {
    "tiktok-mcp": {
      "command": "node",
      "args": [
        "path\\build\\index.js"
      ],
      "env": {
        "TIKNEURON_MCP_API_KEY": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
      }
    }
  }
}

Available Tools

3 tools
tiktok_get_post_detailsB

Get the details of a TikTok post.This is used for getting the details of a TikTok post.Supports TikTok video url (or video ID) as input.Returns the details of the video like - Description - Video ID - Creator username - Hashtags - Number of likes, shares, comments, views and bookmarks - Date of creation - Duration of the video - Available subtitles with language and source information

ParametersJSON Schema
NameRequiredDescriptionDefault
tiktok_urlYesTikTok video URL, e.g., https://www.tiktok.com/@username/video/1234567890 or https://vm.tiktok.com/1234567890, or just the video ID like 7409731702890827041

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It lists many return fields (likes, shares, comments, etc.), which is helpful, but does not disclose authentication, rate limits, or potential errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is moderately concise but has redundancy (first two sentences say similar things). It lists return fields in a bullet-like manner, which aids readability.

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?

Given the tool has one parameter and no output schema, the description adequately covers input and output fields. However, it lacks context on error handling, authentication, or pagination if applicable.

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 schema already describes the parameter in detail, including URL formats and video ID example. The description adds minimal extra value; it mentions 'supports TikTok video url (or video ID)' which matches the schema.

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 clearly states it gets post details and lists specific returned fields, distinguishing it from sibling tools like tiktok_get_subtitle and tiktok_search. However, the first two sentences are redundant.

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?

It implies use when post details are needed and specifies input formats (URL or video ID), but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives.

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

tiktok_get_subtitleA

Get the subtitle (content) for a TikTok video url.This is used for getting the subtitle, content or context for a TikTok video.Supports TikTok video url (or video ID) as input and optionally language code from the tool post detailsReturns the subtitle for the video in the requested language and format.If no language code is provided, the tool will return the subtitle of automatic speech recognition.

ParametersJSON Schema
NameRequiredDescriptionDefault
tiktok_urlYesTikTok video URL, e.g., https://www.tiktok.com/@username/video/1234567890 or https://vm.tiktok.com/1234567890, or just the video ID like 7409731702890827041
language_codeNoLanguage code for the subtitle, e.g., en for English, es for Spanish, fr for French, etc.

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden; it mentions automatic speech recognition fallback but omits other behaviors like rate limits, authorization, or error handling for missing subtitles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description has some redundancy (e.g., 'Get the subtitle...' and 'This is used for getting...'). Could be more concise without losing clarity.

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?

Adequate for a simple tool with two parameters, but lacks details on return format, error handling, and authentication requirements. Not thoroughly complete.

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 parameters are already described. The description adds little beyond the schema, only mentioning the automatic speech recognition fallback for missing language code.

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 clearly states the tool gets subtitles for TikTok videos using a URL or ID. This distinguishes it from siblings like tiktok_get_post_details and tiktok_search.

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?

The description explains the tool is for getting subtitles and mentions optional language code. However, it does not explicitly state when not to use it or compare with alternatives.

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 updates
    • First observedtiktok_get_post_details
    • First observedtiktok_get_subtitle
    • First observedtiktok_search
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

A3.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get post details, get subtitles, and search. No overlap, descriptions are clear and specific.

Naming Consistency5/5

All tools follow a consistent 'tiktok_verb_noun' pattern (get_post_details, get_subtitle, search). Naming is uniform and predictable.

Tool Count4/5

3 tools is appropriate for a focused TikTok MCP that provides core reading operations. Could be slightly expanded, but not under-scoped.

Completeness3/5

Covers search, post details, and subtitles, but missing user profiles, trending, or interaction features. Notable gaps for a comprehensive TikTok tool set.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Bilibili Video Info MCP

    lesir831
    A
    license
    A
    quality
    C
    maintenance
    A Bilibili MCP Server that can retrieve subtitles, danmaku (bullet comments), and comments information from videos using the video URL.
    3
    20
    MIT

  • tiktok-mcp

    PPiai
    F
    license
    B
    quality
    D
    maintenance
    MCP server for TikTok that enables searching videos, users, hashtags, and fetching trending content, user profiles, and video details via official API or public scraping.
    8
    -

  • tiktok-studio-mcp

    aaronckj
    A
    license
    A
    quality
    B
    maintenance
    MCP server for TikTok that publishes videos to your own TikTok account and retrieves video performance metrics through TikTok's official Content Posting and Display APIs.
    6
    36 PyPI
    MIT

Appeared in Searches