Crawlora MCP

tiktok_top_ads_location_info

Read-only

Fetch TikTok's inferred initial Top Ads targeting context for a Creative Center module: initial_country, l1_industry/l2_industry, and first_industry/second_industry metadata when present. Use this when you need TikTok's starting country and industry for a query; use tiktok_top_ads_locations instead to choose from available countries, tiktok_top_ads_filters to choose explicit filters, and tiktok_top_ads_list to fetch ads. It returns context, not country options or ad results.

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

Input Schema

Name	Required	Description	Default
`module`	No	Optional upstream Creative Center module identifier for initial targeting. Omitted or 0 defaults to 1; other nonzero IDs pass through to TikTok without local range validation. Valid IDs are not enumerated by this endpoint.

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.

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / module / description

Previous value: -"Creative Center module id, default 1."New value: +"Optional upstream Creative Center module identifier for initial targeting. Omitted or 0 defaults to 1; other nonzero IDs pass through to TikTok without local range validation. Valid IDs are not enumerated by this endpoint."

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/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 real context beyond that: it clarifies the return is "context, not country options or ad results" and that industry fields appear "when present" (optionality). It does not add auth/rate-limit detail, but the annotation floor is already met.

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?

Purpose is front-loaded in the first clause, followed by usage routing and a return-scope caveat. Three tight sentences with no filler; each sentence carries a distinct load (what it fetches, when to use it, what it does not return).

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?

An output schema exists, so return-value detail is not required, yet the description still clarifies the semantic boundary of the output (context vs. options vs. ads). For a single-optional-param read tool with annotations, nothing an agent needs to call it correctly is missing.

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%, so the single `module` parameter is fully documented in the schema, including the omit-or-0 default and pass-through behavior. The description references "a Creative Center module" but adds no syntax or constraints beyond what the schema already states. Baseline 3 for a fully covered schema.

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?

States a specific verb ("Fetch") and resource ("TikTok's inferred initial Top Ads targeting context") and enumerates the exact returned fields (`initial_country`, `l1_industry`/`l2_industry`, `first_industry`/`second_industry`). It explicitly contrasts itself with the sibling tools, so an agent can distinguish it without opening any 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?

Gives an explicit when-to-use condition ("when you need TikTok's starting country and industry for a query") and names four alternatives with their distinct purposes: `tiktok_top_ads_locations` for country options, `tiktok_top_ads_filters` for filters, and `tiktok_top_ads_list` for ads. Routing is unambiguous.

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?