TikTok Ads by Get MCP Ads

tiktok get audience report

tiktok_get_audience_report

Read-onlyIdempotent

Read TikTok audience performance reports by age or gender at advertiser, campaign, ad group, or ad level to analyze demographic delivery and metric results.

Instructions

Read TikTok AUDIENCE performance reports by age or gender at advertiser, campaign, ad group or ad level, including delivery from eligible Smart+ campaigns. Multiple demographics return separate reports, not a joint distribution. Explicit pagination and native provider errors; no inference of configured targeting or Custom Audience membership.

Input Schema

Name	Required	Description	Default
`page`	No	Page number to request, starting at 1.
`adIds`	No	Restrict results to these ad IDs.
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`endDate`	Yes	Last date of the reporting period, in YYYY-MM-DD format, on or after startDate.
`metrics`	Yes	Native AUDIENCE metric keys, e.g. spend, impressions, clicks, ctr, cpc, conversion. Provider rejects unsupported metric combinations; BASIC metric availability does not imply AUDIENCE support.
`dataLevel`	No	TikTok reporting aggregation level. Metrics and dimensions must be compatible with this level.	AUCTION_CAMPAIGN
`orderType`	No	Sort direction for the selected ordering field.
`startDate`	Yes	First date of the reporting period, in YYYY-MM-DD format.
`adgroupIds`	No	Restrict TikTok results to these ad group IDs.
`dimensions`	Yes	age and/or gender, optionally with the ID matching dataLevel. Multiple demographics return separate reports, never a fabricated age × gender cross-tab.
`orderField`	No	Provider field used to order report rows.
`campaignIds`	No	Restrict results to these campaign IDs.
`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.

Changed15 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / adIds / $ref
```
Removed value: -"#/properties/campaignIds"
```

addedInput schema / properties / adIds / items

Added value: +{
+  "description": "Exact TikTok numeric ID, as a string.",
+  "pattern": "^\\d+$",
+  "type": "string"
+}

addedInput schema / properties / adIds / maxItems
```
Added value: +100
```
addedInput schema / properties / adIds / minItems
```
Added value: +1
```
addedInput schema / properties / adIds / type
```
Added value: +"array"
```
removedInput schema / properties / adgroupIds / $ref
```
Removed value: -"#/properties/campaignIds"
```

addedInput schema / properties / adgroupIds / items

Added value: +{
+  "description": "Exact TikTok numeric ID, as a string.",
+  "pattern": "^\\d+$",
+  "type": "string"
+}

addedInput schema / properties / adgroupIds / maxItems
```
Added value: +100
```
addedInput schema / properties / adgroupIds / minItems
```
Added value: +1
```
addedInput schema / properties / adgroupIds / type
```
Added value: +"array"
```
removedInput schema / properties / endDate / $ref
```
Removed value: -"#/properties/startDate"
```
addedInput schema / properties / endDate / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
addedInput schema / properties / endDate / 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

A3.7/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 the description's job is to add beyond that — and it does: multiple demographics yield separate reports rather than a joint distribution, pagination is explicit, errors are surfaced natively, and it will not infer configured targeting or Custom Audience membership. Those are real behavioral caveats an agent would otherwise get wrong. It stops short of describing result shape or limits, but the output schema covers returns.

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 compact sentences, front-loaded with purpose and scope, with caveats trailing. Slightly dense and clause-heavy, but every clause carries information rather than filler.

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?

For a 13-parameter reporting tool with annotations and an output schema, the description covers what is queried, at which levels, how demographics are returned, and the error/pagination posture. The remaining gap is routing guidance relative to sibling reporting tools, which is minor given full schema and output coverage.

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 the schema already documents all 13 parameters including the dimensions semantics and dataLevel compatibility. The description restates the demographic-separation rule but adds no syntax, default, or format detail beyond the schema — baseline 3 is appropriate.

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 ('Read TikTok AUDIENCE performance reports') plus the breakdown axes (age/gender) and aggregation levels (advertiser → ad), which separates it from sibling list/detail tools like tiktok_get_audiences or tiktok_get_audience_details. It does not explicitly name the closest alternative (tiktok_get_insights), so sibling differentiation is implied rather than stated.

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?

The scope constraints (demographic breakdowns, eligible Smart+ delivery, supported dataLevels) imply when the tool applies, but there is no explicit when-to-use/when-not guidance or named alternative such as tiktok_get_insights for non-demographic reporting. The agent must infer selection from the purpose sentence.

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

Deploy Server