Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_top_ads_spotlight

Fetch hand-picked TikTok Top Ads Spotlight ads from Creative Center, including brand, engagement, CTR, objectives, video details, and paginated results.

Instructions

Retrieve TikTok Top Ads Spotlight. Lists the Top Ads Spotlight materials that TikTok Creative Center hand-picks. page starts at 1; limit defaults to 20 and is capped at 100. Each ad has its title, brand, likes, comments, shares, CTR, objectives and video info. data.pagination gives the page, size, total and has_more.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
limitNoMaximum number of ads to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a fair job: it discloses pagination rules (page starts at 1, limit defaults to 20, capped at 100) and the shape of the returned records including data.pagination. It omits auth/permission requirements and rate limits, but the read-only, paginated nature of the call is clear.

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?

Four short sentences, front-loaded with purpose then parameters then return shape; every sentence adds information. Slightly dense with inline backticked field names but 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?

There is no output schema, so describing returned fields (title, brand, likes, comments, shares, CTR, objectives, video info) and the pagination envelope is necessary and present. Combined with the pagination constraints, an agent has enough to call and consume the tool correctly.

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 schema text is bare ('Page number', 'Maximum number of ads to return'). The description adds real semantics: the 1-based indexing for page and the default (20) plus hard cap (100) for limit, which the schema does not state.

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?

States a specific verb and resource ('Retrieve TikTok Top Ads Spotlight') and defines the subset precisely as the materials TikTok Creative Center hand-picks. That curated scope distinguishes it in spirit from the raw list siblings (tiktok_top_ads_list), though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the scope ('hand-picks'), so an agent can infer this is for the editorial spotlight feed rather than general Top Ads. However, there is no explicit when-to-use, no exclusions, and no pointer to alternatives such as tiktok_top_ads_list or tiktok_top_ads_filters.

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