TikTok Ads by Get MCP Ads

tiktok get insights

tiktok_get_insights

Read-onlyIdempotent

Query TikTok Ads performance insights by metrics, date range, dimensions, and reporting level. Automatically routes age/gender breakdowns to separate 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

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

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

A4/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description's extra value is the planner-selection behavior and the key constraint that multiple audience breakdowns stay as separate reports and are never joined. That is a non-obvious result-shape trait an agent would otherwise get wrong. Pagination/row-limit behavior is left to the schema.

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?

Front-loaded with the core action, then the resource pointers, then the routing exception and the no-join constraint. Every sentence carries information, though 'query planning' is filler jargon that could be dropped.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter reporting tool with an output schema and full annotation coverage, the description supplies exactly the missing pieces: which resources resolve metric/dimension keys, how age/gender dimensions are routed, and that audience breakdowns are never merged. Nothing an agent needs to call it correctly is absent.

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 all 15 parameters including enums and defaults are already documented. The description reinforces reportType auto-defaulting through its routing explanation but adds no syntax or compatibility detail beyond the schema. Baseline 3 applies when the schema carries this much.

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 (query TikTok Ads performance insights) and names the planner/catalog model it runs against. It also names the sibling it delegates to for age/gender breakdowns (tiktok_get_audience_report), so an agent can separate the two without opening schemas. Slightly abstract wording ('query planning') keeps it from a 5.

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

Usage Guidelines4/5

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

Gives concrete routing rules: use tiktok://metrics for metric keys, tiktok://dimensions for dimensions, age/gender dimensions automatically go to the AUDIENCE report, everything else uses the BASIC planner. It stops short of stating when to call tiktok_get_audience_report directly versus letting this tool route.

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

Deploy Server