Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_top_ads_suggestions

Fetch TikTok Top Ads search suggestions from Creative Center to discover trending ad queries by scenario, with optional count.

Instructions

Retrieve TikTok Top Ads suggestions. Returns Top Ads search suggestions from TikTok Creative Center. count is the maximum number of suggestions (default 50) and scenario picks the suggestion scenario id (default 1). The query list can be empty for the default scenario.

Input Schema

NameRequiredDescriptionDefault
countNoMaximum number of suggestions to return
scenarioNoSuggestion scenario id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions defaults for count and scenario, which is helpful, but does not state whether the tool is read-only, whether it requires authentication, or what the response format looks like. It also refers to a 'query list' that does not appear in the input schema, which adds confusion rather than transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are appropriately front-loaded and concise. However, the third sentence about the `query` list is confusing because no such parameter exists in the schema, making the description less efficient and potentially misleading.

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?

For a simple two-parameter retrieval tool with no output schema and no annotations, the description covers the basic purpose and parameter defaults. But it omits usage guidelines, safety profile, and any output shape details, and the mention of an undocumented `query` list creates an unresolved gap.

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 coverage is 100%, so the schema already documents both parameters. The description adds default values (count=50, scenario=1), which is useful, but it also mentions a `query` list that is not part of the schema. That inconsistency undermines the added value, leaving the description only partially helpful beyond the schema.

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 states a clear verb and resource: 'Retrieve TikTok Top Ads suggestions.' It specifies the source (TikTok Creative Center) and distinguishes the output as 'search suggestions.' However, it does not explicitly differentiate from close siblings like tiktok_top_ads_recommend or tiktok_top_ads_spotlight, so an agent must still infer the distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It explains parameter defaults but never states when a caller should choose suggestions over recommendations, spotlight, or list tools. The usage context is implied only by the tool name.

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