Skip to main content
Glama
TikTok Ads by Get MCP Ads

TikTok Ads by Get MCP Ads

tiktok list ad videos

tiktok_list_ad_videos
Read-onlyIdempotent

List an advertiser's full TikTok video library with file names, durations, dimensions, and preview URLs. Use it to browse creative assets before building ads or checking inventory.

Instructions

List the advertiser's whole video library (file/video/ad/search): file name, duration, dimensions, signature, and publicly served preview and cover URLs. Every TikTok URL is signed and expires after roughly six hours: re-resolve with tiktok_get_asset_urls before use.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (page_info.total_page in the response gives the bound)
pageSizeNoItems per page (TikTok caps file library pages at 100)
advertiserIdYesTikTok advertiser ID

Output 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. Changed2 schema fields changedv2.1.1
    • 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"
      +  }
      +]
  2. First observedv2.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond structured data by disclosing that every TikTok URL is signed and expires after roughly six hours, with a remediation path — a behavioral trait no annotation or schema field conveys.

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?

Two sentences, both load-bearing: the first names the resource and output fields, the second carries the expiry warning and remedy. Nothing is repeated and the critical constraint is easy to spot.

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?

With an output schema present, the description need not explain return values, and pagination is covered in the schema. The main remaining gap is that it never positions this tool relative to the other video-retrieval siblings, which an agent would need to choose correctly.

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 page, pageSize, and advertiserId are already fully documented in the schema. The description adds no syntax or semantics for the parameters beyond what the schema supplies, 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 ("List the advertiser's whole video library") and enumerates the returned fields, so the agent knows what comes back without opening the output schema. It does not distinguish this listing tool from close siblings like tiktok_get_video_assets or tiktok_get_uploaded_video, which is the main clarity gap.

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?

The description does route the agent to tiktok_get_asset_urls for re-resolving expired URLs, which is genuine conditional guidance. However, it gives no when-to-use/when-not guidance against the several sibling tools that also surface videos (tiktok_get_video_assets, tiktok_get_uploaded_video), so the core selection decision is left to inference.

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