Crawlora MCP

tiktok_top_ads_list

Read-only

Fetch high-performing auction-ad rows from TikTok Creative Center. Use tiktok_top_ads_analysis for performance signals, tiktok_top_ads_detail for one ad, or tiktok_top_ads_recommend for related ad ideas.

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_top_ads_list"
  }
}

Input Schema

Name	Required	Description
`like`	No	Like percentile bucket id or comma-separated ids. Allowed values: 1 (Top 1~20%), 2 (Top 21~40%), 3 (Top 41~60%), 4 (Top 61~80%), 5 (Top 81~100%).
`page`	No	Result page, default 1.
`limit`	No	Max ads to return, default 20, max 100.
`period`	No	Lookback period in days, default 30. Allowed values: 7, 30, 180.
`keyword`	No	Brand or product keyword search.
`duration`	No	Video duration bucket. Allowed values: time-2 (<10s), time-3 (10-20s), time-4 (20-30s), time-5 (30-40s), time-6 (40-50s), time-7 (>50s).
`industry`	No	Industry filter id or comma-separated ids from the top-ads filters endpoint.
`order_by`	No	Sort order, default for_you. Allowed values: for_you, impression, ctr, play_2s_rate, play_6s_rate, cvr, like.
`ad_format`	No	Ad format id. Allowed values: 1 (Spark ads), 2 (Non-Spark ads).
`objective`	No	Objective filter id or comma-separated ids from the top-ads filters endpoint.
`ad_language`	No	Ad language id or comma-separated ids from the top-ads filters endpoint, e.g. en.
`country_code`	No	Country code or comma-separated ISO-2 codes from the top-ads filters endpoint, e.g. US.
`pattern_label`	No	Pattern label id or comma-separated ids from the top-ads filters endpoint.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds only the 'high-performing auction-ad' scoping phrase; it says nothing about pagination behavior, result caps, or rate limits. Adequate but thin given the low bar set by annotations.

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, zero waste. The core purpose is front-loaded and the sibling routing follows immediately with no filler.

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

Completeness4/5

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

Output schema exists so return values need no explanation, and all 13 params are fully documented in the schema. The description covers purpose and sibling disambiguation; only minor behavioral context (pagination/limits) is absent.

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% across 13 parameters, and each parameter already documents defaults, allowed values and formats. The description adds no parameter-level meaning, so the 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 (Fetch) plus resource and scope (high-performing auction-ad rows from TikTok Creative Center), and names the sibling tools it is not. An agent can distinguish it from tiktok_top_ads_analysis/detail/recommend without opening any 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 to three alternatives by purpose: analysis for performance signals, detail for one ad, recommend for related ideas. Clear context for choosing among siblings, though it never states a when-not condition for this tool itself beyond the implicit listing role.

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

All Crawlora MCP tools Inspect

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

Need Help?