TikTok Ads by Get MCP Ads

tiktok get audience overlap

tiktok_get_audience_overlap

Read-onlyIdempotent

Analyze audience overlap across ad groups, custom audiences, saved audiences, and targeting fields to identify overlapping segments and flag pairs above a threshold.

Instructions

Read-only audience overlap diagnostics across ad groups, custom audiences, saved audiences, and targeting fields.

Input Schema

Name	Required	Description
`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	Optional ad group IDs to compare.
`campaignId`	No	Optional campaign ID filter.
`advertiserId`	Yes	TikTok advertiser ID
`overlapThreshold`	No	Overlap threshold used to flag audience pairs, in the units declared by this schema.
`includeSavedAudiences`	No	Include accessible saved-audience metadata in the overlap analysis.

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.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Read-only' in the description is largely redundant. The description does add the useful disclosure that analysis spans multiple entity types including targeting fields, but says nothing about cost, result size, or how overlapThreshold triggers flagging beyond what the schema states.

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 no filler or repetition. It is perhaps too terse for a seven-parameter diagnostic tool, but there is no wasted language.

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?

Output schema exists, annotations cover the safety profile, and the schema documents all seven parameters, so the description is not required to explain returns. It is, however, complete enough to identify the tool; the missing piece is comparative guidance against sibling audience tools.

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 baseline is 3. The description hints at the entity scope covered by adgroupIds, campaignId and includeSavedAudiences, but adds no semantics for overlapThreshold or smartPlus beyond what the schema already documents clearly.

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?

States a specific verb-and-resource: 'audience overlap diagnostics' scoped to ad groups, custom audiences, saved audiences and targeting fields. An agent can tell it is an overlap analysis read, though it gives no signal to distinguish it from close siblings such as tiktok_get_audience_report or tiktok_get_audiences.

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

Usage Guidelines2/5

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

The description never says when to reach for this tool rather than tiktok_get_audience_report, tiktok_get_audiences, or tiktok_get_targeting, nor does it state preconditions (e.g. needing at least two ad groups to compare). Usage is only implied by the word 'diagnostics'.

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

Deploy Server