Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_top_ads_location_info

Retrieve TikTok Top Ads location info. Returns TikTok's inferred initial country and industry targeting context for Top Ads.

Instructions

Retrieve TikTok Top Ads location info. Returns TikTok's inferred initial country and industry targeting context for Top Ads. Use it when you need starting targeting values; use the locations, filters, and list endpoints to choose criteria and retrieve ads.

Input Schema

NameRequiredDescriptionDefault
moduleNoOptional upstream Creative Center module identifier; omitted or 0 defaults to 1, other nonzero IDs are passed through without local range validation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.12
    • changedInput schema / properties / module / description
      Previous value: -"Creative Center module id"New value: +"Optional upstream Creative Center module identifier; omitted or 0 defaults to 1, other nonzero IDs are passed through without local range validation"
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the returned values are TikTok's *inferred* initial targeting context, which is useful, but it says nothing about read-only status, auth needs, or any side effects. For a simple retrieval tool this is adequate but not rich.

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?

Two tight sentences with the purpose front-loaded and routing guidance second. No waste, and every clause earns its place, though it is not notably structured with a distinct usage block.

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 no output schema and no annotations, the description must explain what is returned, and it does ('inferred initial country and industry targeting context'). For a zero-required-param read tool this is nearly complete, with only the 'module' semantics left to the schema.

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% and the single optional 'module' parameter is fully documented in the schema. The description adds no parameter meaning at all, so the schema does the heavy lifting; baseline 3 is appropriate.

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 specific verb+resource ('Retrieve TikTok Top Ads location info') and clarifies the payload as TikTok's inferred initial country and industry targeting context. It also distinguishes itself from the similarly named tiktok_top_ads_locations sibling by pointing to 'the locations, filters, and list endpoints'. The residual ambiguity in 'location info' (geography vs. targeting context) keeps this from 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?

It gives an explicit when-to-use ('Use it when you need starting targeting values') and names alternatives for other goals ('use the locations, filters, and list endpoints to choose criteria and retrieve ads'). Clear context with alternatives, though no explicit when-NOT-to-use or prerequisites.

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