Skip to main content
Glama

Crawlora MCP

tiktok_creative_center_top_content

Read-only

Returns TikTok Creative Center's current Top Content set - four top-performing branded videos, each with its video object and anonymously fetchable MP4, engagement metrics, author profile and follower count, and by default the video's top comments plus keyword mention counts. The set is a daily snapshot of four objects with no pagination or history; the titles rotate daily. Set include_comments=false for a smaller response with only video, author, and metrics. Requires no cookies or login. Use tiktok_creative_center_videos for the separate trending-videos ranking.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiktok_creative_center_top_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_commentsNoInclude each object's top comments and comment-keyword counts, default true. Set false for a smaller response with only video, author, and metrics.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses that the set is a daily snapshot of exactly four objects, has no pagination or history, rotates titles daily, requires no cookies or login, and that MP4s are anonymously fetchable and comments included by default. These are exactly the behavioral traits an agent needs.

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-loaded with the core purpose, then progressively adds behavioral constraints and the alternative. Every sentence carries distinct information with no filler.

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?

With an output schema present, return values need not be re-explained, and the description covers behavior, defaults, the single parameter, and the sibling alternative. Nothing an agent needs to call this correctly is missing.

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 already 100%, so baseline is 3, but the description adds meaning by stating what the smaller response actually contains (only video, author, and metrics) and that comments are on by default, clarifying the tradeoff beyond the schema wording.

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?

States a specific verb ('Returns') and resource ('TikTok Creative Center's current Top Content set'), then enumerates the exact payload (four branded videos, video object, MP4, engagement metrics, author, comments). It explicitly names the sibling tiktok_creative_center_videos it is not, so an agent can route without opening either 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?

Explicitly routes the agent to tiktok_creative_center_videos for the separate trending-videos ranking, and gives the include_comments=false toggle as a usage decision. It lacks an explicit 'when not to use this' beyond the named alternative, but the context is clear.

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