Crawlora MCP

tiktok_top_ads_suggestions

Read-only

Get TikTok Creative Center Top Ads search suggestions before building a query. Use tiktok_top_ads_list to retrieve matching ads; use tiktok_top_ads_recommend when you already have a material id and want related 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_suggestions"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No	Max suggestions to return, default 50.
`scenario`	No	Suggestion scenario id, default 1.

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.2/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 safety profile is covered. The description adds workflow positioning (a pre-query suggestion step) but says nothing about return shape, pagination, or what the suggestion set contains; with an output schema present, that gap is minor and a 3 is appropriate.

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 padding, and the tool's role is front-loaded ahead of the sibling routing. Every clause earns its place.

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?

With annotations covering safety, an output schema covering returns, and both optional params documented, the description supplies what an agent needs to select and call it. Only the overlap/semantics of the 'scenario' id remain unexplained.

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% for both params (count default 50, scenario default 1), so the schema carries the load. The description adds no parameter detail or examples beyond that, which is the baseline-3 case.

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?

The description states a specific verb and resource ('Get TikTok Creative Center Top Ads search suggestions') and locates it in the workflow ('before building a query'). It also differentiates from sibling tools by naming tiktok_top_ads_list and tiktok_top_ads_recommend, so an agent can place it without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit routing: use tiktok_top_ads_list to retrieve matching ads, and tiktok_top_ads_recommend when you already have a material id. The 'before building a query' framing states the phase this tool belongs to, leaving nothing to inference.

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?