TikTok Ads by Get MCP Ads

tiktok get write context

tiktok_get_write_context

Read-onlyIdempotent

Retrieves exact TikTok entity details, parent settings, and advertiser currency/timezone to validate configuration before editing or building new setups.

Instructions

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

Input 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

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.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is known. The description's 'Read-only' merely repeats readOnlyHint; what it does add is scope of returned context (parent settings, currency/timezone), but it offers no further behavioral detail such as auth or rate-limit traits.

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 with no filler, and the purpose plus timing ('before editing') is front-loaded. Every clause earns its place.

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?

An output schema exists, so return values need not be explained, and the description covers the pre-write use case well. It could be slightly clearer about what 'parent settings' includes or how smartPlus affects the read, but nothing critical for invocation is missing.

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 description coverage is 100% and each parameter already has a description, including the important string-not-number ID constraint and the smartPlus flag. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb (read) plus the resources it returns: the exact entity, parent settings, and advertiser currency/timezone. This distinguishes it from generic list/get tools like tiktok_get_entities_raw or tiktok_get_campaigns, though 'exact TikTok entity' is slightly abstract without saying which fields are returned.

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?

Explicitly says when to call it: 'before editing or building a new configuration.' It does not name an alternative to use instead or state when not to use it, but the pre-write workflow context is clear enough for an agent.

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

Deploy Server