Skip to main content
Glama

tiktok_post

Extracts detailed data from any TikTok post including play counts, likes, comments, shares, video quality, music info, and full author stats.

Instructions

Extracts detailed data for any TikTok post including play counts, likes, comments, shares, video quality details, music info, and full author stats. [Credits: 5 API credits per successful request] Notes: Identify the post either via the (username + post_id) pair or via the single url parameter — one of these two approaches is required. Returns: { id, canonical_url, description, created_at, location, privacy, statistics: {plays, likes, comments, shares, collects}, video: {width, height, duration, quality, codec, play_url, download_url, subtitles[]}, music: {id, title, author, duration, audio_url, cover}, author: {id, username, verified, followers, following, likes, video_count}, hashtags: [{id, name}], mentions[], categories[], suggested_words[] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFull TikTok post URL, used instead of passing `username` and `post_id` separately. Example: `https://www.tiktok.com/@nba/video/7255379108241198378`.
post_idNoThe ID of the post to get data for. Required unless the `url` parameter is used (must be paired with username).
usernameNoThe username of the TikTok profile whose post you want to scrape. Required unless the `url` parameter is used (must be paired with post_id).
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the return structure and credit cost, but does not explicitly state that the tool is read-only, nor does it mention potential errors, rate limits, or authentication needs.

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

Conciseness4/5

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

The description is concise and front-loaded with the main purpose, though the return structure is presented as a dense block. Overall, it avoids redundancy and is efficiently structured.

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 tool's moderate complexity, the description covers the key aspects: purpose, parameters, credit cost, and return format. No output schema exists, but the inlined return structure compensates. It is sufficiently complete for agent usage.

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% with good descriptions, and the description adds value by explaining the two identification approaches and providing an example URL, making parameter usage clearer.

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 extracts detailed data for any TikTok post, listing specific fields like play counts, likes, comments, etc. However, it does not explicitly differentiate from sibling tools like tiktok_profile or scrape_post.

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 description explains the two parameter approaches (url or username+post_id) and mentions credit cost, but does not provide guidance on when to use this tool over alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alessandrobenigni/ScrapingDog-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server