Skip to main content
Glama

Crawlora MCP

tiktok_top_ads_spotlight

Read-only

Returns Top Ads Spotlight materials handpicked by TikTok Creative Center. limit: Max ads to return, default 20, max 100. page: Result page, default 1. Use tiktok_top_ads_list to retrieve TikTok Top Ads.

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

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, default 1.
limitNoMax ads to return, default 20, max 100.

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. First observed

TDQS

A3.6/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 safety is covered. The description adds the Spotlight provenance and pagination defaults but says nothing about auth requirements, rate limits, or result cap behavior beyond the schema's max.

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?

Three short sentences, purpose front-loaded, no filler. The parameter restatements duplicate the schema rather than adding value, which is the only inefficiency.

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?

An output schema exists so return values need no explanation, and both optional params are documented. For a simple read-only paged endpoint the definition is essentially complete, with only the general Top Ads routing hinting left thin.

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% and both parameters already carry descriptions in the schema. The description restates the same defaults and max verbatim, adding no new semantics such as how paging interacts with the result set.

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 ('Returns Top Ads Spotlight materials handpicked by TikTok Creative Center') and explicitly distinguishes itself from tiktok_top_ads_list. The word 'materials' is slightly vague about what the payload actually contains, keeping it short of a 5.

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 an implicit when-to-use via the contrast with tiktok_top_ads_list, telling the agent that this tool is for the handpicked Spotlight set and that the sibling covers general TikTok Top Ads. It does not address the other nearby siblings (tiktok_top_ads_recommend, tiktok_top_ads_suggestions), so the routing picture is only partly drawn.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources