AdsAgent — TikTok Ads MCP

List and refresh advertiser pixels

assets_list_pixels

Destructive

List cached TikTok pixels for the authenticated tenant with their owning BC list attached. Each row carries linked_bcs: [{bc_id, bc_name}, ...] derived from linked_advertiser_ids → advertiser.owner_bc_id plus any direct owner_bc_id from BC-asset-sourced rows.

Returns a compact bounded page. Optional: cursor from the previous response, limit (default 20, maximum 50), and search (case-insensitive native id/name lookup). Keep the same tool, filters and limit while following next_cursor serially until complete=true. A rejected or old cursor requires restarting page one. complete describes pagination, not upstream sync coverage or permission to create.

For creation, pass advertiser_id from assets_list_ad_accounts to return only assets with an exact cached advertiser link. Shared BC ownership alone is not an advertiser link. The prepare step still verifies the selected asset, identity type and create-capable authorization.

Assets are not swept on a schedule. With advertiser_id, an empty cached result is checked live against TikTok once for that advertiser; pass refresh=true (first page, advertiser_id required) to re-read it even when cached rows exist. coverage.live_refresh reports refreshed, rate_limited, no_permission (TikTok refuses this advertiser; do not create on it), no_connection or failed.

REQUIRED: none. EXAMPLE: assets_list_pixels({"search": "purchase"})

A live refresh can replace cached pixel rows for the selected advertiser.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`search`	No
`refresh`	No
`advertiser_id`	No
`connection_context`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / refresh

Added value: +{
+  "default": false,
+  "title": "Refresh",
+  "type": "boolean"
+}

First observedSep 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, indicating a mutation-capable tool. The description adds that a live refresh can replace cached pixel rows, which is useful context. However, it doesn't explicitly flag the destructive/overwrite nature as strongly as it could, and coverage.live_refresh outcomes are described but not the full impact.

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?

The description is dense but well-organized, front-loading the core purpose and then detailing pagination, refresh behavior, and the creation path. It's longer than minimal but each paragraph covers a distinct concern.

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 6 parameters, no output schema, and 0% schema coverage, the description does a good job covering pagination, refresh semantics, coverage.live_refresh outcomes, and the advertiser_id requirement. It's missing connection_context and doesn't fully explain what the returned row structure looks like beyond linked_bcs.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate. It explains cursor (from previous response), limit (default 20, max 50), search (case-insensitive native id/name lookup), advertiser_id (from assets_list_ad_accounts, required for refresh), and refresh (first page, advertiser_id required). It doesn't explain connection_context, but overall adds substantial meaning beyond the bare schema.

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 the tool lists cached TikTok pixels for the authenticated tenant with owning BC lists attached, and explains the linked_bcs derivation. It distinguishes itself from siblings like assets_list_ad_accounts and assets_refresh_all by focusing on pixel listing with BC linkage.

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

Usage Guidelines4/5

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

The description explains when to use advertiser_id (for creation, to get exact cached advertiser links) and when to use refresh (first page, advertiser_id required). It also warns that shared BC ownership is not an advertiser link and that the prepare step verifies authorization. Alternatives aren't explicitly named, but the usage context is clear.

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?