TikTok Ads by Get MCP Ads

tiktok get adgroups

tiktok_get_adgroups

Read-onlyIdempotent

Retrieve complete TikTok ad group configurations, including targeting, audiences, placements, budget, and schedule. Supports Smart+ targeting specs with pagination for large accounts.

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

TableJSON 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

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.4/5.0

Behavior5/5

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

Beyond the annotations, the description adds valuable behavior disclosure: 'Missing fields are unknown, not unrestricted targeting' clarifies the open-world semantics, and 'Paginated' sets pagination expectations. The smartPlus:true note also explains a mode switch that differs from the default classic read, all while remaining consistent with the readOnly/idempotent annotations.

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?

Three sentences, each carrying distinct information: what is read, the Smart+ special case, and the missing-fields caveat plus pagination. No filler or repetition of schema details, making it compact and front-loaded.

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 rich annotations, a full input schema, and an output schema, the description covers the important behavioral notes that are not in structured data. It could additionally mention when to prefer a sibling tool, but the core information an agent needs to invoke the tool correctly is present.

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 schema already documents all six parameters, including the smartPlus behavior and defaults. The description mentions smartPlus:true and pagination, but adds little per-parameter meaning beyond what the schema provides, so baseline 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 opens with the specific verb 'Read' and targets a precise resource: 'full native ad group configuration', then enumerating major contents (targeting, audiences, geo, language, age/gender, placements, budget, schedule). This clearly distinguishes the tool from siblings like tiktok_get_ads or tiktok_get_campaigns by identifying exactly which resource is returned.

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?

The use case is clear: call this when you need the full native ad group configuration, including targeting and budget details. It also gives explicit guidance for Smart+ ad groups via 'Set smartPlus:true', though it does not explicitly mention when not to use it or name sibling alternatives.

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

Deploy Server