Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_creative_center_videos

Fetch TikTok Creative Center trending videos by country, period, sort order, and content tags to analyze ranked TikTok trends.

Instructions

Retrieve TikTok Creative Center trending videos. Returns TikTok Creative Center's ranked trending videos for a country, period, sort order, and optional content tags. TikTok reports the true result-set size (see total_count/page_count in the response) but gates access to it behind a logged-in TikTok One account: an anonymous request always receives page 1 (4 videos) regardless of sort order or period. Country coverage is uneven: only US, JP, ID, VN, and TH have a regional edge host that returns populated results; other countries return an empty videos array (a genuine no-data response, not an error). See the filters endpoint for the complete country, period, sort, and content tag value lists.

Input Schema

NameRequiredDescriptionDefault
periodNoLookback window in days
sort_byNoSort order
country_codeYesISO-2 country code
organic_onlyNoRestrict to organic (non-paid) videos only
content_label_idNoDeprecated: single content tag id; use content_label_ids instead
content_label_idsNoContent tag ids to filter by, repeatable; matches videos carrying any selected tag

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.13
    • changedInput schema / properties / content_label_id / description
      Previous value: -"Content tag id to filter by"New value: +"Deprecated: single content tag id; use content_label_ids instead"
    • addedInput schema / properties / content_label_ids
      Added value: +{
+  "description": "Content tag ids to filter by, repeatable; matches videos carrying any selected tag",
+  "items": {
+    "enum": [
+      "11002",
+      "11003",
+      "11010",
+      "11013",
+      "11015"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / period / enum
      Added value: +[
+  7,
+  30
+]
    • addedInput schema / properties / sort_by / enum
      Added value: +[
+  "views",
+  "engagement",
+  "six_second_views"
+]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the entire behavioral burden and does so richly: it discloses the logged-in gating that forces anonymous callers to page 1 (4 videos), that total_count/page_count reflect the true result-set size, and that an empty videos array is a genuine no-data response rather than an error. This is exactly the context an agent cannot get from structured fields.

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?

Dense single paragraph that is front-loaded with the core purpose before the caveats. Every sentence contributes (gating, count semantics, country coverage, filter referral), though the density is near the upper bound of comfortable length.

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?

For a read tool with no annotations and no output schema, the description covers everything an agent needs: return-shape behavior (total_count/page_count), the empty-response edge case, access limitations, and where to find valid filter values. Nothing material 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 100%, so the baseline is 3, but the description adds genuine parameter-relevant knowledge beyond the schema: only US, JP, ID, VN, and TH produce populated results, which directly guides country_code usage. It also references the filters endpoint as the source of valid enum values.

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+resource ('Retrieve TikTok Creative Center trending videos') and enumerates the scoping dimensions (country, period, sort, content tags). It also names the sibling 'filters endpoint', letting an agent distinguish this from tiktok_creative_center_filters and the hashtags/top_content siblings without opening a 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 clear operating context and routes the agent to the filters endpoint for valid country/period/sort/tag values. It implicitly establishes when results will be useful (the five supported countries) but does not explicitly say when to prefer this over the sibling trending-content tools, so it stops short of full when/when-not framing.

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