TikTok Ads by Get MCP Ads

tiktok get audience details

tiktok_get_audience_details

Read-onlyIdempotent

Retrieve custom, lookalike, and saved audience details for a TikTok advertiser, optionally filtering by audience IDs. Use it to inspect DMP audience targeting data in read-only mode.

Instructions

Get custom/lookalike/saved audience details where TikTok DMP endpoints are accessible. Read-only only.

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.
`audienceIds`	No	Optional custom/lookalike audience IDs. If omitted, lists available audiences.
`advertiserId`	Yes	TikTok advertiser ID
`includeSavedAudiences`	No	Also include saved audience targeting details when available.

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

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so "Read-only only" adds no information beyond structured fields. The only genuine addition is "where TikTok DMP endpoints are accessible," which hints at an availability gate but never explains what happens for non-DMP advertisers or how access is determined.

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?

Two short sentences with the verb and scope front-loaded; nothing is buried. The second sentence is largely redundant with the readOnlyHint annotation, so it does not fully earn its place.

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?

Output schema and annotations carry the return-shape and safety burden, and the schema documents all params, so the definition is callable as-is. What is missing is the sibling disambiguation (this vs tiktok_get_audiences) and any explanation of the DMP accessibility condition, both of which materially affect tool selection.

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 each of the four parameters is already documented in the schema (including the audienceIds/listing tradeoff and the includeSavedAudiences flag). The description adds no parameter-level meaning, which is acceptable given the baseline but leaves no extra value.

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 names a specific verb (Get) and resource (audience details) and enumerates the audience types covered (custom/lookalike/saved), so an agent knows what data comes back. However, it never distinguishes itself from close siblings like tiktok_get_audiences or tiktok_get_audience_overlap, which an agent could easily confuse it with.

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?

"Read-only only" is a safety restatement, not guidance on when to pick this tool. There is no mention of when to use tiktok_get_audiences instead, nor any prerequisite about DMP access other than a vague caveat phrase.

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

Deploy Server