tiktok-ads-mcp-server

Overview Schema Source Related Servers Discussions Admin

tiktok get audience report

tiktok_get_audience_report

Read-onlyIdempotent

Fetch TikTok audience performance reports by age or gender at advertiser, campaign, ad group, or ad level. Returns separate demographic reports for targeting analysis.

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

TableJSON 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

TableJSON 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.

Addedv2.0.0Sep 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description goes beyond this by disclosing that multiple demographics return separate reports (not a joint distribution), that pagination and native provider errors are explicit, and that the tool does not infer configured targeting or Custom Audience membership. This is meaningful behavioral context, though it doesn't cover rate limits or response-size nuances, which the output schema may partially address.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences with no fluff. The first sentence front-loads the core action, resource, and scope; the second clarifies an important behavioral nuance; the third covers error/pagination behavior and a key limitation. Every sentence earns its place and the structure supports quick scanning.

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?

Given the tool's complexity (13 parameters, 5 required, output schema present, annotations provided), the description is largely complete. It covers the operation, scope, demographic behavior, pagination/errors, and non-inference caveats. The only minor gap is that it does not explicitly mention metric/dimension compatibility with data levels, but the schema descriptions already address that, so the description does not need to duplicate it.

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 every parameter already has a description in the input schema. The description restates the key semantic point about separate reports for multiple demographics, which is already present in the dimensions parameter description. It does not add new parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description states a specific verb ('Read'), a precise resource ('TikTok AUDIENCE performance reports'), and the key dimensions (age/gender) and levels (advertiser, campaign, ad group, ad). It distinguishes itself from siblings like tiktok_get_audience_details and tiktok_get_audience_overlap by focusing on performance reports by demographics, and the Smart+ eligibility note adds valuable scope.

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 usage context is clear: an agent would call this when needing age/gender audience performance reports. It also states limitations (separate reports, no inference of targeting or Custom Audience membership), which guides expectations. However, it never explicitly names alternatives or gives 'when not to use' guidance relative to sibling tools like tiktok_get_audience_details, so the routing is implied rather than explicit.

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

Deploy Server