Skip to main content
Glama
get-mcp-ads

TikTok Ads by Get MCP Ads

tiktok get video assets

tiktok_get_video_assets
Read-onlyIdempotent

Retrieve ad-linked TikTok video asset metadata from ad and video material endpoints. Use ad IDs, video IDs, or ad group filters to return available assets for an advertiser.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adIdsNoOptional ad IDs to inspect.
limitNoMaximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
videoIdsNoOptional video IDs to look up directly in material endpoints.
adgroupIdNoOptional ad group ID filter.
advertiserIdYesTikTok advertiser ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. First observedv2.0.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds some behavioral context by naming the underlying endpoints and suggesting conditional availability ('when available'), but it does not describe edge cases like empty results or error behavior.

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?

The description is a single, front-loaded sentence with no filler or redundancy. It immediately states the action and resource, making it efficient for an agent to parse.

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?

While the output schema covers return shape and annotations cover safety, the description lacks guidance on how this tool relates to sibling asset-listing tools and what 'ad-linked' specifically means in terms of linkage (e.g., via adIds vs videoIds). This leaves some ambiguity for an agent selecting among similar tools.

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 already documented in the schema. The description does not add any parameter-level semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 clearly states a specific verb ('Return') and resource ('ad-linked TikTok video asset metadata') from named endpoints. It is distinguishable from many siblings by emphasizing 'ad-linked' and 'video asset metadata', but it does not explicitly name alternative tools or contrast with them.

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?

The description provides no explicit guidance on when to use this tool versus the many sibling tools (e.g., tiktok_list_ad_videos, tiktok_get_asset_urls). 'When available' hints at a condition but does not explain the intended use case or exclusions.

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