AdsAgent — TikTok Ads MCP

List and refresh advertiser identities

assets_list_identities

Destructive

List cached TikTok posting identities for the authenticated tenant. Meta pages analog: call this from assets discovery before campaigns_quick_create when ad_params lacks identity_id / identity_type (Smart+ App may auto-pick only when exactly one eligible BC_AUTH_TT row exists for the advertiser). Each row includes regular_local_media_eligible=true only when its exact identity_type is CUSTOMIZED_USER; regular local video/image also requires its exact advertiser link. AUTH_CODE is Spark-only on regular create: use an eligible Spark post and pass its signed receipt unchanged when available; a legacy receipt-less item incurs one bounded live provider verification before approval. TT_USER and BC_AUTH_TT are not regular-local choices and may be used only on a server-verified compatible Smart+ route. When the same identity_id appears on multiple BC rows, pass identity_authorized_bc_id from this list. Each row carries linked_bcs: [{bc_id, bc_name}, ...].

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_identities({"limit": 20})

A live refresh can replace cached identity 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

A4.7/5.0

Behavior5/5

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

Annotations declare destructive=true but not what is destroyed; the description fills that gap by stating a live refresh can replace cached identity rows, and it documents permission/auth outcomes (coverage.live_refresh values including no_permission), rate limiting, and the one-off live verification behavior. This is substantial context beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose is front-loaded, but the body is a dense wall of domain jargon crammed into long parenthetical run-ons. The information earns its place, yet the presentation is hard to parse and would benefit from tighter scoping or structure.

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?

For a 6-parameter tool with no output schema, the description covers pagination completion semantics, row fields (linked_bcs, regular_local_media_eligible), the coverage.live_refresh status vocabulary, and refresh caveats. An agent has what it needs to page, filter, and refresh correctly.

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?

With 0% schema description coverage, the description carries the burden and largely does: it gives limit defaults/maximum, cursor semantics and restart-on-rejection, search as case-insensitive native id/name, refresh requiring first page + advertiser_id, and advertiser_id scoping. Only connection_context is left undocumented.

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?

States a specific verb and resource up front ('List cached TikTok posting identities for the authenticated tenant') and extends it with the refresh capability. It also distinguishes itself from the surrounding asset-list siblings by naming the 'Meta pages analog' and its role in the discovery-before-create flow.

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?

Explicit about when to call it: 'call this from assets discovery before campaigns_quick_create when ad_params lacks identity_id / identity_type'. It also names the alternative source (assets_list_ad_accounts for advertiser_id) and the exclusion (shared BC ownership alone is not an advertiser link).

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?