AdsAgent — TikTok Ads MCP

creatives_list

List creatives owned by the authenticated tenant with cursor pagination. This is the TikTok AdsAgent tenant library (tiktok.adsagent.md Creatives), not Meta adsagent.md and not TikTok Ads Manager Material Center. READY_LOCAL dashboard rows belong here and are create sources via creative.creative_id; they do not need a TikTok image_id/video_id until after confirm. For images, use one creative_id for one image or ordered creative.image_creative_ids (2..35 JPEG/PNG images) for one carousel; every member must be an eligible image row. ad_params.creative_list contains separate variants, not the ordered cards of one carousel. Rows omit content hashes and storage keys. The legacy download_url is retained as an authenticated same-origin endpoint only after storage verification; unverified historical ready rows report verification_pending. Inspect coverage (create_eligible_count / empty_reason / next_action) plus readiness.create_eligible before using creative_id in campaigns_quick_create. An empty page with coverage.empty_reason=no_tenant_creatives is the only true empty-library signal (unfiltered scope=library plus a tenant-wide existence check). no_creatives_in_query means the current folder/search/media_type/time_filter matched nothing; no_creatives_in_root means scope=root was empty while the tenant owns creatives elsewhere — retry scope=library (default) or call creatives_list_folders. Trust coverage.scope.kind; never describe a root/folder page count as the whole library. Do not treat those as a different tenant.

REQUIRED: none. Optional: scope (library|root, default library — entire tenant library across root and folders; use root for root-only reads), folder_id (str — UUID of one folder), cursor (opaque and scope-bound; reuse it only with the identical query), limit (int 1..50, default 20), search (filename substring, max 200 chars), media_type (all/image/video), time_filter (all/24h/7d/30d), include_incomplete (bool, default true). Returns count, complete, meta.has_more, next_cursor and snapshot_at (legacy top-level has_more remains). Each row exposes creative_id as an alias of id for direct creative.creative_id selection. These describe library pagination, not TikTok upload completion; continue serially with next_cursor instead of client fan-out. EXAMPLE: creatives_list({"search": "hero", "media_type": "video", "limit": 20})

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`scope`	No	library
`cursor`	No
`search`	No
`folder_id`	No
`media_type`	No	all
`time_filter`	No	all
`include_incomplete`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 17, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and delivers: returned fields, row omissions, legacy download_url auth behavior, verification_pending status, and empty-page semantics. It also warns against misinterpreting folder/root counts as 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but appropriately dense and well-structured: purpose, exclusions, caveats, compact parameter summary, return fields, and an example. Each section adds information not available in the schema, and the example makes the invocation concrete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, plus the high complexity around carousels, empty-reason semantics, readiness fields, and pagination, the description is remarkably complete. It equips an agent to call the tool correctly and interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema provides no descriptions or enums, so the description compensates fully. It documents every optional parameter with types, allowed values, ranges, defaults, and semantic caveats such as cursor scope-binding and folder_id UUID format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: 'List creatives owned by the authenticated tenant with cursor pagination.' It explicitly distinguishes this tool from Meta adsagent.md, TikTok Ads Manager Material Center, and related creatives tools, making its role unambiguous.

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

Usage Guidelines5/5

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

It gives concrete usage conditions: retry scope=library or call creatives_list_folders when no_creatives_in_root, inspect coverage/readiness before downstream use, and continue serially with next_cursor instead of fan-out. It also states what this tool is not for, clarifying selection among alternatives.

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

All AdsAgent — TikTok Ads MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?