Retrieve available TikTok Top Ads locations and list country filters for ad targeting. Returns each country's ID, name, label, and conversion flag.
Retrieve TikTok Top Ads locations. Lists the country filters offered by TikTok Creative Center Top Ads. Each country has an id such as US, a value (the country name), a label and a has_conversion flag. Takes no parameters.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations the description carries the full burden, and it discloses the shape of the response (id like 'US', value, label, has_conversion flag) plus the fact that it is parameterless and read-only in nature. It omits auth/permission or rate-limit context, but the return-shape disclosure is genuinely useful given there is no output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four short sentences, front-loaded with the purpose before the return-shape detail. Nothing is wasted, though the field enumeration could be trimmed slightly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless lookup with no output schema, the description covers purpose and returned fields adequately. It would be stronger if it noted how the returned country IDs are meant to be consumed downstream.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so baseline is 4. The description confirms 'Takes no parameters,' which matches the empty schema and removes any ambiguity for the caller.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Retrieve') and resource ('TikTok Top Ads locations') and clarifies it lists the country filters offered by TikTok Creative Center Top Ads. It distinguishes itself from the other tiktok_top_ads_* siblings by resource (locations vs analysis/detail/filters/list), though it never names an alternative explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: an agent can infer this is a lookup for country IDs to feed other Top Ads calls, but there is no explicit when-to-use statement, no exclusion, and no named alternative such as tiktok_top_ads_filters or tiktok_top_ads_location_info.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.