TikTok Ads by Get MCP Ads

tiktok get targeting catalog

tiktok_get_targeting_catalog

Read-onlyIdempotent

Retrieve TikTok targeting and planning catalogs—locations, languages, interests, behaviors, hashtags, devices, and time zones—to validate or build ad targeting options.

Instructions

Read TikTok targeting and planning catalogs: locations, languages, interests, behaviors, hashtags, Search Ads keyword ideas/health, devices, carriers, contextual tags, content exclusions, and time zones.

Input Schema

Name	Required	Description
`query`	No	Search text used to find matching entries in the selected catalogue.
`catalog`	Yes	Allowlisted targeting dictionary or catalog to inspect.
`parameters`	No	Additional native parameters documented for the selected GET endpoint
`advertiserId`	No	TikTok advertiser account ID as a string.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / parameters / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that this is a catalog/reference lookup rather than campaign data, which is useful, but says nothing about pagination, result caps, or advertiser-scoped catalog requirements.

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?

A single front-loaded sentence with the verb and resource first, followed by an enumeration that earns its length by conveying breadth of catalogs. Slightly list-heavy but not padded.

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?

With an output schema and fully described parameters, the definition is mostly self-sufficient. However, for a tool with 17 catalog options where some (search_keyword_ideas, search_campaign_health) presumably require an advertiserId, the description leaves that conditional context and the query-required cases unstated.

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 all four parameters (including the catalog enum and the free-form 'parameters' object) are already documented, establishing a baseline of 3. The description's catalog list largely restates the enum and adds no new meaning about how query text or the pass-through 'parameters' object behave per catalog.

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 uses a specific verb ('Read') plus a defined resource ('TikTok targeting and planning catalogs') and enumerates the catalog families available, so the scope is concrete. It stops short of distinguishing itself from close siblings such as tiktok_get_targeting or tiktok_search_keywords, so an agent must still infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by 'Read ... catalogs' — the description never states when to reach for this tool instead of tiktok_get_targeting (targeting settings) or tiktok_search_keywords (keyword research). No prerequisites (e.g. which catalogs need an advertiserId) are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server