Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

tiktok_top_ads_list

Fetch high-performing TikTok auction ads from Creative Center by keyword, industry, country, period, format, or sort order to research ad creatives.

Instructions

Retrieve TikTok Top Ads. Returns high-performing auction ads from TikTok Creative Center. The service defaults period to 30, page to 1, limit to 20, and order_by to for_you. Use /tiktok/top-ads/filters for dynamic enum values and static enums for order, duration, likes, and ad format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
likeNoLike percentile bucket id or comma-separated ids
pageNoPage number
limitNoMaximum number of ads to return
periodNoLookback period in days
keywordNoBrand or product keyword search
durationNoVideo duration bucket
industryNoIndustry filter id or comma-separated ids from /tiktok/top-ads/filters
order_byNoSort order
ad_formatNoAd format id
objectiveNoObjective filter id or comma-separated ids from /tiktok/top-ads/filters
ad_languageNoAd language id or comma-separated ids from /tiktok/top-ads/filters
country_codeNoCountry code or comma-separated country codes from /tiktok/top-ads/filters
pattern_labelNoPattern label id or comma-separated ids from /tiktok/top-ads/filters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.17.5
    • addedInput schema / properties / ad_format / enum
      Added value: +[
      +  "1",
      +  "2"
      +]
    • addedInput schema / properties / duration / enum
      Added value: +[
      +  "time-2",
      +  "time-3",
      +  "time-4",
      +  "time-5",
      +  "time-6",
      +  "time-7"
      +]
    • addedInput schema / properties / like / enum
      Added value: +[
      +  "1",
      +  "2",
      +  "3",
      +  "4",
      +  "5"
      +]
    • addedInput schema / properties / order_by / enum
      Added value: +[
      +  "for_you",
      +  "impression",
      +  "ctr",
      +  "play_2s_rate",
      +  "play_6s_rate",
      +  "cvr",
      +  "like"
      +]
    • addedInput schema / properties / period / enum
      Added value: +[
      +  7,
      +  30,
      +  180
      +]
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must cover behavioral traits. It discloses default values for period, page, limit, and order_by, and notes that dynamic enums come from a filters endpoint. However, it doesn't describe return format or pagination behavior, which is acceptable for a read-only list but not exhaustive.

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?

Two sentences with no redundancy. The purpose is front-loaded, and the second sentence efficiently covers defaults and filter guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 13 optional parameters and no output schema, the description provides helpful defaults and filter guidance but doesn't explain how to combine filters or what the response structure looks like. It's adequate but could be more complete for a complex tool with many filtering options.

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%, but the description adds value by stating defaults for four parameters and clarifying which enums are static versus dynamic. This goes beyond the schema's field descriptions.

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 the action (Retrieve TikTok Top Ads) and the resource (high-performing auction ads from TikTok Creative Center). It is specific enough to distinguish from a detail or analysis tool, though it doesn't explicitly name sibling alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus other TikTok ad tools. It only mentions using /tiktok/top-ads/filters for enum values, which is about parameter values, not tool selection. It lacks exclusions or alternatives.

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