TikTok Ads by Get MCP Ads

tiktok list advertisers

tiktok_list_advertisers

Read-onlyIdempotent

List all TikTok advertiser accounts accessible with your current token, returning each advertiser's ID, name, and status.

Instructions

List all TikTok advertiser accounts accessible with the current token. Returns advertiser ID, name, and status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON 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.

First observedv2.0.1Sep 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context about token scoping ('accessible with the current token') and the returned fields. It does not describe pagination or error behavior, but those are less critical given the strong annotation coverage and presence of an output schema.

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 short sentences deliver purpose, scope, and return fields with no filler. The main action and scope are front-loaded, and every word contributes meaning.

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 zero-parameter, read-only list operation with annotations and an output schema already present, the description covers what an agent needs: what is listed, token scoping, and the returned fields. No prerequisites or missing caveats are needed for correct invocation.

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?

The input schema has zero parameters and schema coverage is 100%, so there is no parameter ambiguity for the description to resolve. The description appropriately says nothing about parameters, and the 0-param baseline of 4 applies.

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 uses the specific verb 'List all' with a clear resource ('TikTok advertiser accounts') and a scope constraint ('accessible with the current token'). It also states the exact returned fields (advertiser ID, name, status), making the tool's purpose immediately distinguishable from siblings like tiktok_get_advertiser_info.

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 implies the right use case: when an agent needs the full set of advertiser accounts under the current token. However, it does not explicitly mention when to prefer this over sibling tools like tiktok_get_advertiser_info or asset-listing tools, nor does it name any exclusions or alternatives.

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

Deploy Server