TikTok Ads by Get MCP Ads

tiktok get video assets

tiktok_get_video_assets

Read-onlyIdempotent

Fetches ad-linked TikTok video asset metadata from ad/get and video material endpoints by advertiser ID. Filter by ad, ad group, or video ID to inspect available assets.

Instructions

Return ad-linked TikTok video asset metadata from ad/get and video material endpoints when available.

Input Schema

Name	Required	Description
`adIds`	No	Optional ad IDs to inspect.
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`videoIds`	No	Optional video IDs to look up directly in material endpoints.
`adgroupId`	No	Optional ad group ID filter.
`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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral fact: results are assembled from two endpoint families and only returned 'when available', implying the response may be partial or empty. It does not say what happens when an ad has no video asset or how the two sources are merged.

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 padding or redundancy. It is efficient, though the trailing 'when available' is vague enough that it slightly weakens an otherwise tight statement.

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?

An output schema exists, so return-value structure needn't be described, and the annotations carry the safety profile. What remains thin is behavior when no assets are found and how the two sources combine, but for a read-only metadata fetch this is close to complete.

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 each of the five parameters is already documented, which sets the baseline at 3. The description adds marginal meaning by implying two lookup paths (ad-linked via adIds versus direct material lookup via videoIds), but does not explain how adIds and videoIds interact or which wins.

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 states a specific verb ('Return') and resource ('ad-linked TikTok video asset metadata'), so the agent knows what it retrieves. However, it doesn't distinguish this from close siblings such as tiktok_list_ad_videos, tiktok_get_asset_urls, or tiktok_get_uploaded_video, leaving overlap ambiguous. Naming the upstream endpoints ('ad/get and video material endpoints') is implementation detail rather than differentiation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many video/creative siblings, nor any stated prerequisites or exclusions. 'When available' is a hedge about data presence, not a usage condition that helps the agent choose.

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

Deploy Server