TikTok Ads by Get MCP Ads

tiktok get targeting

tiktok_get_targeting

Read-onlyIdempotent

Read configured ad group targeting and audience references—custom/lookalike inclusions/exclusions, geo, language, age, gender, placements, interests, behaviors—for classic or Smart+ ad groups.

Instructions

Read configured ad group targeting and audience references: custom/lookalike inclusions/exclusions, geo, language, age/gender, placements, interests and behaviors. Supports classic and upgraded Smart+ (smartPlus:true), preserving targeting_spec and automatic targeting settings. Does not infer delivered audiences or hidden Smart+ signals. Use tiktok_get_audiences for audience names/types and tiktok_get_audience_report for delivered demographics.

Input Schema

Name	Required	Description
`page`	No	Page number to request, starting at 1.
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`smartPlus`	No	Use true for upgraded Smart+ ad groups: reads their native targeting_spec and exact placements via smart_plus/adgroup/get. No fallback to classic settings.
`adgroupIds`	No	Restrict TikTok results to these ad group IDs.
`campaignId`	No	Exact TikTok numeric ID, as a string.
`advertiserId`	Yes	Exact TikTok numeric 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.

Changed6 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / adgroupIds / items / $ref
```
Removed value: -"#/properties/campaignId"
```
addedInput schema / properties / adgroupIds / items / description
```
Added value: +"Exact TikTok numeric ID, as a string."
```
addedInput schema / properties / adgroupIds / items / pattern
```
Added value: +"^\\d+$"
```
addedInput schema / properties / adgroupIds / items / type
```
Added value: +"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

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds genuinely value-adding behavior: Smart+ support, preservation of targeting_spec and automatic targeting settings, and the caveat that it will not infer delivered audiences or hidden Smart+ signals. It does not describe output shape or pagination behavior, but the output schema covers the former.

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?

Front-loaded with purpose, then capability, then exclusion, then alternatives — each sentence carries weight. The mid-sentence enumeration of targeting fields is dense but useful rather than padding.

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 a full input schema, an output schema and read-only annotations, the description supplies what structured fields cannot: the classic vs. Smart+ distinction and the explicit non-coverage of delivered/hidden signals. Remaining gaps are the unmentioned targeting-catalog sibling and no word on pagination expectations for multi-adgroup reads.

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 baseline is 3. The mention of 'smartPlus:true' and native smart_plus/adgroup/get reads restates what the parameter description already says in detail rather than adding new semantics for the other five parameters.

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?

Specific verb (read) plus resource (configured ad group targeting), followed by an explicit enumeration of the targeting dimensions covered (custom/lookalike, geo, language, age/gender, placements, interests/behaviors). It also names the two nearest siblings it is not, so an agent can distinguish it without opening a schema.

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?

'Use tiktok_get_audiences for audience names/types and tiktok_get_audience_report for delivered demographics' gives explicit routing plus the negative boundary ('Does not infer delivered audiences'). The closest confusable sibling, tiktok_get_targeting_catalog, is never mentioned, which keeps this just short of full routing coverage.

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

Deploy Server