Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_creative_center_top_content

Fetches TikTok Creative Center's daily top branded videos with MP4/cover URLs, metrics, author profiles, and optional comments plus keyword counts.

Instructions

Retrieve TikTok Creative Center top content. Returns TikTok Creative Center's current Top Content set: four top-performing branded videos, each with the video object (anonymous MP4 and cover URLs), engagement metrics, the author profile and follower count, and (by default) the video's top comments plus keyword mention counts derived from them. The set is a daily snapshot and there is no pagination or historical query; the four titles rotate when the snapshot changes. Set include_comments=false for a smaller response with only video, author, and metrics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_commentsNoInclude each object's top comments and comment-keyword counts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: it discloses the fixed cardinality (four videos), the daily snapshot with rotating titles, the absence of pagination/history, the default inclusion of comments and comment-keyword counts, and what the include_comments=false variant returns. This is exactly the behavioral context an agent needs before calling.

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-loads the purpose in the first sentence, then layers payload contents, snapshot semantics, and the parameter tradeoff. Every sentence contributes distinct information with no redundancy.

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?

No output schema or annotations exist, so the description must convey the return shape and constraints, and it does: it enumerates returned fields (video object with MP4/cover URLs, engagement metrics, author profile/follower count, comments, keyword counts). Complete for an agent to call correctly.

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 schema documents the boolean, but the description goes beyond it by stating the default (comments included by default) and the concrete effect of setting it false (smaller response with only video, author, and metrics). That added meaning justifies above the baseline 3.

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?

Specific verb ('Retrieve') plus a precisely scoped resource ('TikTok Creative Center Top Content set'), immediately clarified as four top-performing branded videos. An agent knows exactly what it gets without opening the schema, and the specificity distinguishes it from broader siblings like tiktok_creative_center_videos.

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?

It gives useful operational context (daily snapshot, no pagination, no historical query, titles rotate), which tells the agent when the tool is and isn't appropriate. However, it never names a sibling alternative or states an explicit when-to-use-vs-other-tools rule, so guidance remains implied rather than routing-level.

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

Deploy Server

Other Tools