Skip to main content
Glama

SocialDataX TikTok MCP

by com.52choujiang
OverviewDiscussionsAdmin

tiktok_get_user_info_by_profile_url

Read-only

根据 TikTok 用户主页链接获取用户公开资料。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_urlYes非空 TikTok 用户主页链接，例如 https://www.tiktok.com/@teamtrump

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioYes用户简介；当前不可用时为空字符串
nameYes用户昵称；当前不可用时为空字符串
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
user_idYesTikTok 用户 ID；长数字字符串，原样保留，不要转为数字；当前不可用时为空字符串；不要用它代替 tiktok_id 或 profile_url
verifiedYes用户是否为认证账号
tiktok_idYesTikTok 号，即用户主页 @ 后的标识；当前不可用时为空字符串，为空时不要作为用户标识使用
avatar_urlYes用户头像链接；当前不可用时为 null
profile_urlYes用户主页链接；当前不可用时为 null
follower_countYes粉丝数；当前不可用时为 null
following_countYes关注数；当前不可用时为 null
private_accountYes用户账号是否为私密账号
received_like_countYes用户作品累计获赞数；当前不可用时为 null
posted_content_countYes用户已发布作品数；当前不可用时为 null

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / profile_url / description
      Previous value: -"TikTok 用户主页链接，例如 https://www.tiktok.com/@teamtrump"New value: +"非空 TikTok 用户主页链接，例如 https://www.tiktok.com/@teamtrump"
    • addedInput schema / properties / profile_url / minLength
      Added value: +1
    • addedInput schema / properties / profile_url / pattern
      Added value: +".*\\S.*"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation against external data. The description adds only that the result is public profile data, which is useful but minimal context beyond 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 a single, front-loaded sentence that states the resource and the required input type with zero waste. It is appropriately sized for a simple one-parameter tool.

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?

Given the low complexity, full schema documentation, and the presence of an output schema, the description covers the essential purpose and input. It is only slightly incomplete because it lacks usage guidance relative to the sibling tools.

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 the single parameter is fully documented with an example in the schema. The description does not add any format, parsing, or validation details beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: fetching public profile information by TikTok homepage URL. This implicitly distinguishes it from the sibling tool that fetches by TikTok ID, but it does not explicitly name alternatives or clarify scope beyond the tool name.

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 phrase '根据 TikTok 用户主页链接' implies the tool is used when a profile URL is available, giving an implied usage condition. However, there is no explicit when-to-use guidance, no exclusions, and no mention of the alternative tiktok_get_user_info_by_tiktok_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