Skip to main content
Glama

SocialDataX TikTok MCP

by com.52choujiang
OverviewDiscussionsAdmin

tiktok_search_posts

Read-only

搜索 TikTok 作品，可返回视频和图片作品。用户需要按搜索词查找作品时使用； 已有作品链接时直接使用详情或评论工具；已有 post_id 且需要评论时直接使用按 ID 评论工具，均无需先调用搜索； 从搜索结果继续时，可复用其中的 share_url 或 post_id； 支持 content_type 筛选、过滤用户卡片等非作品结果，并支持 page_token 翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes非空搜索词，可传关键词或短语，例如品牌名、话题、人物名或产品名；不要传作品链接、用户主页链接、post_id、tiktok_id 或 page_token。
page_tokenNo请求分页令牌是不透明令牌。请求的 page_token 为空字符串表示首页；继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。
content_typeNo作品类型筛选：all 不限作品类型，可返回视频和图片作品；video 只返回视频作品；image 只返回图片作品。继续翻页时必须保持同一 content_type。all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes当前页 TikTok 作品搜索结果，已过滤用户卡片等非作品结果；当前页可能为空，是否继续翻页以 next_page_token 是否为空为准
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
next_page_tokenYes响应分页令牌是不透明令牌。响应的 next_page_token 为空字符串表示没有更多结果；非空时必须将完整令牌原样作为下一次请求的 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"搜索词，可传关键词或短语，例如品牌名、话题、人物名或产品名；不要传作品链接、用户主页链接、post_id、tiktok_id 或 page_token。"New value: +"非空搜索词，可传关键词或短语，例如品牌名、话题、人物名或产品名；不要传作品链接、用户主页链接、post_id、tiktok_id 或 page_token。"
    • addedInput schema / properties / keyword / minLength
      Added value: +1
    • addedInput schema / properties / keyword / pattern
      Added value: +".*\\S.*"
    • changedInput schema / properties / page_token / description
      Previous value: -"分页令牌。首页传空字符串；next_page_token 为空字符串表示没有更多结果。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；它是不透明令牌，不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。"New value: +"请求分页令牌是不透明令牌。请求的 page_token 为空字符串表示首页；继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。"
    • changedOutput schema / properties / next_page_token / description
      Previous value: -"分页令牌。首页传空字符串；next_page_token 为空字符串表示没有更多结果。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；它是不透明令牌，不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。"New value: +"响应分页令牌是不透明令牌。响应的 next_page_token 为空字符串表示没有更多结果；非空时必须将完整令牌原样作为下一次请求的 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。"
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description adds real behavioral context beyond them: it returns both video and image posts, filters out user cards and other non-post results, and supports page_token pagination. It does not discuss rate limits or result caps, keeping it just 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.

Conciseness5/5

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

Front-loaded with the core action, then layered guidance and constraints, each sentence carrying distinct information (routing rules, continuation reuse, filtering, pagination). No redundancy or filler despite the length.

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 an output schema exists, return values need not be described. The description covers routing, filtering behavior, pagination continuation and result reuse, leaving no material gap for a read-only search tool with fully documented parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 and the schema already documents keyword, page_token and content_type in depth. The description adds meaning the schema does not: content_type semantics as a filter, the non-post result filtering, and the instruction to reuse share_url/post_id when continuing from results, which guides downstream calls.

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?

States a specific verb and resource ('搜索 TikTok 作品') and immediately scopes the result set ('可返回视频和图片作品'). It further distinguishes itself from siblings by naming the detail and comment tools it is not, so an agent can route without opening any schema.

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?

Explicit when-to-use ('用户需要按搜索词查找作品时使用') and two explicit when-not-to-use cases with named alternatives: existing post link → detail/comment tools, existing post_id → comment-by-ID tool, '均无需先调用搜索'. It also explains how to continue from a prior search by reusing share_url/post_id.

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

All SocialDataX TikTok MCP toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources