Skip to main content
Glama

SocialDataX TikTok MCP

tiktok_get_post_detail_by_url

Read-only

根据 TikTok 作品页面链接获取视频或图片作品详情。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesTikTok 作品页面链接,例如 https://www.tiktok.com/@user/video/123 或 https://www.tiktok.com/@user/photo/123;视频和图片作品均可返回详情,不要用 post_id 代替 url

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
musicYes作品音乐;当前不可用时为 null
titleYes作品标题;图片作品可能有标题,视频作品或当前不可用时为 null
videoYes视频播放资源;图片作品或当前不可用时为 null
authorYes作品作者信息
imagesYes图片作品的图片资源列表;视频作品为空数组
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
post_idYesTikTok 作品 ID;长数字字符串,原样保留,不要转为数字;content_type=video 时标识视频作品;content_type=image 的 post_id 标识图片作品,不能作为视频作品 ID 使用
share_urlYesTikTok 作品页面链接;视频作品为视频页面链接,图片作品为图片作品页面链接;不要把 content_type=image 的 share_url 当作视频页面链接;当前不可用时为 null
like_countYes点赞数;当前不可用时为 0
play_countYes播放/浏览数;当前不可用时为 0
topic_tagsYes作品话题标签列表;name 不含 #;topic_id 当前仅作为结果标识返回,不要用 topic_id 代替话题名称
descriptionYes作品文案;没有文案或当前不可用时为空字符串
share_countYes分享数;当前不可用时为 0
content_typeYes作品类型:video 表示视频作品,image 表示图片作品
publish_timeYes发布时间,秒级 Unix 时间戳;当前不可用时为 0
collect_countYes收藏数;当前不可用时为 0
comment_countYes评论数;当前不可用时为 0
cover_image_urlYes作品封面图片资源链接;可能随时间失效;不是作品页面链接或播放资源链接;当前不可用时为 null

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds that both video and photo posts are supported, but it does not disclose further behavioral traits such as rate limits, authentication needs, or failure behavior. It does 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 one efficient, front-loaded sentence with no redundant wording. It conveys the verb, resource, and supported content types in minimal space.

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?

For a single-parameter, read-only lookup with a rich input schema, existing annotations, and an output schema, the description is complete enough for an agent to select and invoke the tool correctly. No critical information needed for basic use is missing.

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 has 100% parameter description coverage, including examples and an explicit instruction not to pass post_id instead of url. The tool description only restates that the lookup is URL-based and adds no extra semantic value beyond the schema.

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 a specific verb ('获取') and a specific resource (TikTok 作品详情), and explicitly scopes the tool to video and photo post URLs. This makes it easy to distinguish from sibling tools that fetch comments, user info, or post lists.

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 intended use is implied: use this when you have a TikTok post page URL and need post details. However, the description does not explicitly say when to prefer this over siblings like tiktok_get_post_comments_by_url or tiktok_get_user_info_by_profile_url, nor does it mention exclusion criteria.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources