TikTok Ads by Get MCP Ads

tiktok get async report status

tiktok_get_async_report_status

Read-onlyIdempotent

Check a TikTok async report task status by taskId and advertiser ID to confirm report readiness without creating or changing reports.

Instructions

Check a TikTok async report task status by taskId when async report endpoints are available. No report creation or mutation is performed.

Input Schema

Name	Required	Description	Default
`taskId`	Yes	Async report task ID returned by TikTok report task creation outside this read-only MCP.
`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, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description's 'no report creation or mutation is performed' merely restates those hints and adds nothing about polling cadence, what a pending/failed status looks like, or error behavior for an unknown taskId.

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 short sentences with the resource and key parameter front-loaded and no filler. The 'when async report endpoints are available' clause is slightly vague but occupies little space.

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 both parameters are schema-documented. However, for a status-polling tool the description omits the practically important context — whether repeated calls are expected, how terminal states are indicated, and what happens for an expired or invalid taskId.

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%: both advertiserId and taskId are documented in the schema, including that taskId originates from task creation outside this MCP. The description only echoes 'by taskId' and adds no format, validity, or cross-parameter meaning, so baseline 3 applies.

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 ('Check a TikTok async report task status') keyed to a named parameter ('by taskId'), which no sibling tool in the list covers. The qualifier 'when async report endpoints are available' introduces an odd conditional but does not obscure the core action.

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?

Implies the usage context (polling a task created elsewhere) and explicitly excludes creation/mutation, but names no alternative tool and gives no when-not guidance or prerequisite ordering. The schema, not the description, is what tells the agent taskId must come from outside this MCP.

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

Deploy Server