TikTok Ads by Get MCP Ads

tiktok list ad images

tiktok_list_ad_images

Read-onlyIdempotent

Lists an advertiser's image library with file name, dimensions, signature, carousel usability, and a temporary public image URL for ad creative review.

Instructions

List the advertiser's whole image library (file/image/ad/search): file name, dimensions, signature, carousel usability, and a publicly served image URL signed for roughly thirty days (image_url_expires_at gives the exact instant).

Input Schema

Name	Required	Description
`page`	No	Page number (page_info.total_page in the response gives the bound)
`pageSize`	No	Items per page (TikTok caps file library pages at 100)
`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

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower — and the description still adds real value by disclosing that image URLs expire in roughly thirty days and that image_url_expires_at carries the exact instant. That is a non-obvious operational trait an agent must know before caching or reusing a URL. It stops short of covering pagination behavior across the whole library.

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 zero filler; the resource and scope come first and the returned-field detail follows. The parenthetical endpoint path and expiry clause are dense but each earns its place.

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 enumerate return values, yet it summarizes the key ones and adds the expiry caveat that the output schema would not make obvious on its own. Complete enough for a read-only paginated list tool; only the absence of sibling routing keeps it from a 5.

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 coverage is 100%, with all three parameters documented including bounds and TikTok's 100-item page cap, so the baseline of 3 applies. The description adds nothing about advertiserId scope or paging strategy beyond what the schema already states.

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?

Names a specific verb and resource ("List the advertiser's whole image library") and even cites the backing endpoint (file/image/ad/search), so the agent knows exactly what is returned. Sibling differentiation is implicit rather than explicit — tiktok_list_ad_videos is the obvious contrast, but the description never names it.

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 word "whole" implies an unfiltered full-library enumeration, which is useful context, but there is no statement of when to reach for this versus tiktok_list_ad_videos, tiktok_get_creatives, or tiktok_get_asset_urls. No exclusions or prerequisites are given, so usage must be inferred.

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

Deploy Server