Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

tiktok_creative_center_videos

Read-only

Returns TikTok Creative Center's ranked trending videos for a country, period, sort order, and optional content tags, with per-video views, engagement rate, 6-second view-through rate, author profile, and cover images. TikTok reports the true result count but gates deeper pages behind a logged-in TikTok One account: an anonymous request returns the first 4 videos only, and only US, JP, VN, TH, and ID return populated results. country_code: Required. ISO-2 country code, e.g. US. period: 7 (default) or 30 days. sort_by: views (default), engagement, or six_second_views. content_label_ids: Optional repeatable content tag ids from tiktok_creative_center_filters. Use tiktok_creative_center_hashtags to retrieve TikTok Creative Center trending hashtags.

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": {
      "country_code": "<country_code>"
    },
    "name": "tiktok_creative_center_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoLookback window in days, default 7. Allowed values: 7, 30.
sort_byNoSort order, default views. Allowed values: views, engagement, six_second_views.
country_codeYesRequired. ISO-2 country code, e.g. US. See /tiktok/creative-center/filters for the five countries with video trends.
organic_onlyNoRestrict to organic (non-paid) videos only, default false.
content_label_idNoOptional content tag id to filter by. Prefer content_label_ids when filtering by more than one tag.
content_label_idsNoOptional content tag ids to filter by, repeatable or comma-separated, at most 5, OR'd together. Allowed values: 11002, 11003, 11010, 11013, 11015. See /tiktok/creative-center/filters for the tag names.

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. Changed3 schema fields changed
    • changedInput schema / properties / content_label_id / description
      Previous value: -"Optional content tag id to filter by."New value: +"Optional content tag id to filter by. Prefer content_label_ids when filtering by more than one tag."
    • addedInput schema / properties / content_label_ids
      Added value: +{
+  "description": "Optional content tag ids to filter by, repeatable or comma-separated, at most 5, OR'd together. Allowed values: 11002, 11003, 11010, 11013, 11015. See /tiktok/creative-center/filters for the tag names.",
+  "items": {
+    "description": "Documented values: 11002, 11003, 11010, 11013, 11015.",
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • changedInput schema / properties / country_code / description
      Previous value: -"Required. ISO-2 country code, e.g. US."New value: +"Required. ISO-2 country code, e.g. US. See /tiktok/creative-center/filters for the five countries with video trends."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds high-value behavior: the true count is reported but deeper pages require a logged-in TikTok One account, and only five countries yield populated results. These operational caveats go well beyond the safety hints.

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?

Front-loads the core purpose and return shape before the constraints, and every sentence carries weight. It is dense and repeats some schema-level parameter detail, but nothing is wasted.

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, the description needn't explain return values, yet it names the key metrics and adds the anonymous/login and country gating that an agent must know before calling. Nothing an agent needs to invoke it correctly is missing.

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%, so the schema already documents defaults and allowed values for period, sort_by, country_code, organic_only, and the content_label_id(s) fields. The description largely restates these (ISO-2 example, defaults, allowed values) rather than adding new semantics, so baseline 3 applies.

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 and resource ('Returns TikTok Creative Center's ranked trending videos') and enumerates the scoping inputs and the returned per-video fields. It also names the sibling tiktok_creative_center_hashtags as the different resource, so an agent can separate it from related tools 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?

Explicitly routes tag ids to tiktok_creative_center_filters and trending hashtags to tiktok_creative_center_hashtags, and gives the crucial usage constraints (anonymous = first 4 videos, only US/JP/VN/TH/ID return data). It stops short of a clean 'use this when X, not Y' statement, so it's clear context rather than full routing.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources