TikTok Ads by Get MCP Ads

tiktok get write context

tiktok_get_write_context

Read-onlyIdempotent

Fetch existing TikTok entity details, parent settings, and advertiser currency/timezone to guide safe configuration updates.

Instructions

Read the exact TikTok entity, parent settings and advertiser currency/timezone before editing or building a new configuration. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`level`	Yes	Entity level to inspect.
`entityId`	Yes	Exact TikTok numeric ID as a string, never a rounded JavaScript number.
`smartPlus`	No	Use the dedicated upgraded Smart+ endpoints rather than classic endpoints.
`advertiserId`	Yes	Exact TikTok numeric ID as a string, never a rounded JavaScript number.

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 cover readOnly, idempotent, openWorld, and non-destructive behavior. The description adds useful context about what is read (entity, parent settings, currency/timezone) beyond the annotations, which is valuable for agents deciding whether to call this tool. No contradictions with annotations.

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?

A single, front-loaded sentence with zero redundancy. It states the purpose and usage context efficiently without wasting words.

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 an output schema exists and annotations cover safety, the description is sufficient. It clearly explains the purpose, usage timing, and scope of what is read, so an agent has everything needed to call it correctly.

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% per context signals, so the schema fully documents all four parameters. The description does not add syntax or format details beyond what the schema provides, so a baseline 3 is appropriate.

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 clearly states the tool reads the exact TikTok entity, parent settings, and advertiser currency/timezone, which is a specific verb+resource. It also frames it as a pre-write step ('before editing or building'), distinguishing it from general read tools among the many get_* siblings.

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?

It gives a clear usage context: 'before editing or building a new configuration.' This implies when to use it, but it does not explicitly name alternative tools or state when not to use it, falling short of a 5.

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

Deploy Server