Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_top_ads_safety

Retrieve Creative Center safety configuration flags for TikTok ad searches, covering keyword, hashtag, creator, and sound search settings.

Instructions

Retrieve TikTok Top Ads safety configuration. Returns the Creative Center safety configuration flags for search: top_ads_search, keyword_search, hashtag_search, creator_search, sound_search and cc_banner_key. It carries feature flags only, not ad materials. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It does disclose that the payload is feature flags only and not ad materials, and that it takes no parameters, which is meaningful context for a read operation. However it omits any statement about authentication, rate limits, or caching behavior for a configuration endpoint.

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, front-loaded with purpose and followed by the returned flag names and a scoping clarification. The enumerated flag list is long but informative rather than filler; sizing is appropriate.

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

Completeness5/5

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

No output schema exists, so the description must convey return content, and it does by naming the exact configuration flags (top_ads_search, keyword_search, hashtag_search, creator_search, sound_search, cc_banner_key). For a zero-parameter read tool, this is complete enough to invoke and interpret.

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?

The tool has zero parameters, which sets the baseline at 4. The description explicitly confirms 'Takes no parameters,' reinforcing what the empty schema already shows, so nothing is left ambiguous.

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 safety configuration') and clarifies it returns Creative Center safety flags rather than ad materials, which usefully separates it from ad-content siblings. It does not name any sibling tool, so the differentiation is inferential rather than explicit.

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 says what the tool returns but never states when to call it, in what scenario it is appropriate, or how it relates to sibling tools like tiktok_top_ads_filters or tiktok_top_ads_list. No when-to-use or when-not-to-use guidance is present.

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