TikTok Ads by Get MCP Ads

tiktok get insights

tiktok_get_insights

Read-onlyIdempotent

Query TikTok Ads performance insights using the native metric and dimension catalog; age and gender dimensions route automatically to audience reports.

Instructions

Query TikTok Ads performance insights using the current native/calculated metric catalog and query planning. Use tiktok://metrics resource to see available metrics. Use tiktok://dimensions for dimensions. Age/gender dimensions route automatically to AUDIENCE reports via tiktok_get_audience_report, including campaign/ad group levels. Other dimensions use the BASIC planner. Multiple audience breakdowns remain separate reports, never joined.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	AUDIENCE report page; follow nextPage.
`adIds`	No	Restrict AUCTION_AD reports to these ad IDs, including daily trends.
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`endDate`	Yes	End date YYYY-MM-DD
`metrics`	Yes	Metric keys from tiktok://metrics (e.g., spend, impressions, clicks)
`dataLevel`	No	TikTok reporting aggregation level. Metrics and dimensions must be compatible with this level.	AUCTION_CAMPAIGN
`orderType`	No	Native sort direction; defaults to DESC when orderField is selected.
`startDate`	Yes	Start date YYYY-MM-DD
`adgroupIds`	No	Restrict audience reports to these ad groups.
`dimensions`	No	Dimension keys from tiktok://dimensions (e.g., stat_time_day, campaign_id)
`orderField`	No	Order the native report before limiting rows. Include this metric in metrics.
`reportType`	No	Defaults to AUDIENCE for age/gender, BASIC otherwise. Explicit BASIC with demographics is rejected.
`campaignIds`	No	Restrict audience reports to these campaigns.
`advertiserId`	Yes	TikTok advertiser ID
`queryLifetime`	No	Query lifetime metrics (cannot use time dimensions)

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.

First observedv2.0.1Sep 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description's burden is lower. It adds genuinely valuable behavioral context beyond the schema: automatic routing of age/gender to AUDIENCE reports, the 'never joined' guarantee for multiple audience breakdowns, and the existence of query planning. No contradictions with annotations. A 4 rather than 5 because it doesn't disclose error behavior, rate limits, or when queries become async (a sibling async-status tool exists).

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?

Four sentences, each earning its place: purpose in the first sentence, resource lookup in the second, routing in the third, and the no-join caveat in the fourth. The structure is front-loaded and logical. A 4 rather than 5 because the opening mention of 'query planning' is never elaborated, leaving a slightly vague concept in the most important sentence.

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 15-parameter tool with an output schema and safety annotations, the description covers the critical judgment points: where to source valid metric/dimension keys, how report types are chosen, and how the tool relates to the audience-report sibling. What's missing is modest — no mention of pagination beyond what the schema's 'follow nextPage' already says, no async/rate-limit behavior. Given the output schema and annotations pick up the rest, this is reasonably complete.

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 description does add some semantic value by instructing the agent to consult tiktok://metrics and tiktok://dimensions for valid keys (which enriches the metrics and dimensions parameters) and by encoding the reportType routing rule (explicit BASIC with demographics is rejected). However, the schema already documents date formats, limits, enums, and defaults, so the description isn't carrying a heavy parameter load. A 3 is correct.

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 opens with a specific verb+resource pair ('Query TikTok Ads performance insights') and immediately frames the tool as a catalog-driven query planner. It differentiates itself from the tiktok_get_audience_report sibling by explicitly stating that age/gender dimensions route to that tool, and it also distinguishes itself from the raw report tools in the sibling list. The purpose is unambiguous and well-scoped.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use routing rules: age/gender dimensions go through tiktok_get_audience_report, other dimensions use the BASIC planner, and audience breakdowns are never joined. It also tells the agent where to look up valid metrics and dimensions (tiktok://metrics and tiktok://dimensions), which is practical selection guidance rather than leaving it to inference. This is strong alternative-routing information.

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

Deploy Server