TikTok Ads by Get MCP Ads

tiktok get adgroups

tiktok_get_adgroups

Read-onlyIdempotent

Retrieve complete native TikTok ad group settings—targeting, audiences, exclusions, geo, placements, budget, and schedule—with Smart+ support and pagination.

Instructions

Read full native ad group configuration including targeting, custom/lookalike audience references and exclusions, geo, language, age/gender, placements, interests/behaviors, budget and schedule. Set smartPlus:true for upgraded Smart+ targeting_spec. Missing fields are unknown, not unrestricted targeting. Paginated.

Input Schema

Name	Required	Description
`page`	No	Page number to request, starting at 1.
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`smartPlus`	No	Use true for upgraded Smart+ ad groups: reads their native targeting_spec and exact placements via smart_plus/adgroup/get. No fallback to classic settings.
`adgroupIds`	No	Restrict TikTok results to these ad group IDs.
`campaignId`	No	Exact TikTok numeric ID, as a string.
`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.

Changed6 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / adgroupIds / items / $ref
```
Removed value: -"#/properties/campaignId"
```
addedInput schema / properties / adgroupIds / items / description
```
Added value: +"Exact TikTok numeric ID, as a string."
```
addedInput schema / properties / adgroupIds / items / pattern
```
Added value: +"^\\d+$"
```
addedInput schema / properties / adgroupIds / items / 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.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description's value is in what it adds: 'Missing fields are unknown, not unrestricted targeting' prevents a serious misinterpretation of empty results, and the smartPlus note warns there is no fallback to classic settings. Pagination is also disclosed. Only rate-limit/scope behavior is absent.

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 sentences, front-loaded with the resource and its field inventory, then the two operational caveats. The field list is dense but each item discriminates the tool's scope; nothing is redundant padding.

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?

An output schema exists, so return values need not be explained. Combined with 100% parameter coverage and read-only annotations, the description supplies exactly what is missing: pagination, the smartPlus read path, and the semantics of absent targeting fields.

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 advertiserId, campaignId, adgroupIds, page, limit and smartPlus are all documented in the schema. The description's smartPlus sentence largely restates the schema's own explanation, so it adds little beyond the baseline.

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 (read) and resource (native ad group configuration) and enumerates the concrete contents: targeting, audience references/exclusions, geo, language, age/gender, placements, budget, schedule. This clearly separates it from tiktok_get_campaigns and tiktok_get_ads by resource level, though it never names a sibling explicitly.

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?

Usage is implied rather than stated: read ad groups when you need their configuration. The one real routing hint is 'Set smartPlus:true for upgraded Smart+ targeting_spec,' but there is no guidance on when to prefer tiktok_get_targeting or tiktok_get_entities_raw instead, and no exclusions.

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

Deploy Server