Skip to main content
Glama

TikTok profile

tiktok_profile
Read-onlyIdempotent

Get a public TikTok profile: exact follower, following, like and video counts, nickname, bio and bio link, verified badge, region and language, business and organization flags, and its newest videos (up to 15) with plays, likes, comments and captions. A private account's profile is returned without videos. For older videos, call tiktok_videos with the next_cursor returned here.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "tiktok_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesA TikTok username (nasa), @nasa, or a profile link (https://www.tiktok.com/@nasa).
include_media_urlsNoAlso return picture, video and sound file links (long links that expire after a while). Leave it off unless you need the files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the bar is lowered, and the description still adds real behavior: a 15-video cap on embedded media, a private account returning the profile with no videos, and the existence of a next_cursor for pagination. It does not mention rate limits, auth requirements, or error behavior for an invalid username.

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?

Two sentences, no filler: the first front-loads what you get, the second handles the exception (private account) and the pagination hand-off. The long field enumeration is dense but earns its place by telling the agent exactly what data is available.

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?

With no output schema, the description carries the return-shape burden and does so by naming the returned fields and the pagination cursor. What is missing is failure semantics — invalid or nonexistent username, or whether a private profile is distinguishable from an empty one.

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 schema already explains the flexible username formats (bare handle, @handle, profile URL) and the include_media_urls tradeoff. The description adds nothing about either parameter, which is acceptable given full schema coverage but is the baseline, not a value-add.

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?

Opens with a specific verb+resource ("Get a public TikTok profile") and then enumerates the exact fields returned — follower/following/like/video counts, nickname, bio, verified badge, region, business flags, plus the newest 15 videos. An agent can distinguish this from tiktok_videos (single-video list) and the instagram_*/youtube_* siblings 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing for a concrete sub-case: "For older videos, call tiktok_videos with the next_cursor returned here," which names the alternative and the condition selecting it. It also sets expectations for private accounts. No exclusion guidance for other profile-like tools, but the multi-platform siblings are self-evidently distinct.

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