TikTok Ads by Get MCP Ads

tiktok get delivery status

tiktok_get_delivery_status

Read-onlyIdempotent

Aggregate campaign, ad group, and ad delivery status with operation status and diagnostics. Filter by advertiser, campaign, or ad group to troubleshoot delivery issues.

Instructions

Aggregate campaign, ad group, and ad delivery status/operation_status with simple diagnostics.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`adgroupId`	No	Optional ad group ID filter.
`campaignId`	No	Optional campaign ID filter.
`includeAds`	No	Include ad-level status diagnostics.
`advertiserId`	Yes	TikTok advertiser ID

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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the operation aggregates across three levels and includes operation_status plus diagnostics, which is useful, but says nothing about pagination behavior, result volume, or latency despite it being an open-world API call.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification for a tool spanning three entity levels.

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

Completeness3/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, and parameters are fully documented. However, for a cross-level aggregation tool the description never clarifies what "simple diagnostics" actually surfaces or how includeAds changes granularity, leaving a gap in the agent's ability to predict what it will get back.

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 five parameters are documented in the schema; the baseline of 3 applies. The description loosely maps to campaignId/adgroupId/includeAds by naming campaign, ad group, and ad levels, but adds no meaning beyond the schema (e.g., how filters interact across aggregation levels).

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?

The description names a concrete verb ("Aggregate") and concrete resources (campaign, ad group, ad delivery status/operation_status), so an agent can tell this is a roll-up status view rather than an entity list. It does not explicitly distinguish itself from siblings like tiktok_get_campaigns or tiktok_get_adgroups, which return entities rather than status, so differentiation is only implied.

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?

"with simple diagnostics" hints at a triage/monitoring use case, but the description never states when to prefer this over tiktok_get_ads, tiktok_get_campaigns, or tiktok_health_check, nor any preconditions. Usage is inferable from the name and context signals rather than stated.

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

Deploy Server