TikTok Ads by Get MCP Ads

tiktok health check

tiktok_health_check

Read-onlyIdempotent

Verify TikTok Ads credentials and advertiser access with a read-only health check that returns advertiser info but never exposes tokens or secrets.

Instructions

Read-only health check for TikTok credentials, accessible advertisers, and advertiser info. Never returns tokens or secrets.

Input Schema

Name	Required	Description	Default
`advertiserId`	No	Advertiser ID to verify. Defaults to TIKTOK_ADVERTISER_ID, then the first accessible advertiser.

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

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds a genuinely useful guarantee beyond the schema: 'Never returns tokens or secrets', which tells the agent the output is safe to surface. It stops short of saying what happens on auth failure or how the check reports problems.

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 tight sentences, front-loaded with the read-only scope and the key security guarantee. No filler or restatement of the title.

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 an output schema present and annotations covering the safety profile, the description needs only to frame purpose and constraints, which it does. It could be slightly more complete by noting failure modes (e.g., whether an invalid advertiser ID errors or is reported in the response), but nothing essential 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?

The single optional advertiserId parameter is fully documented in the schema (100% coverage), including its fallback chain to TIKTOK_ADVERTISER_ID and then the first accessible advertiser. The description adds no parameter guidance, so baseline 3 applies since the schema carries the load.

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 diagnostic verb ('health check') plus the exact resources it inspects: credentials, accessible advertisers, and advertiser info. This distinguishes it from siblings like tiktok_get_advertiser_info and tiktok_list_advertisers, which return data rather than validating access.

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 implied use case (verify credentials/advertiser access before running other calls) is clear from 'health check', but the description never states when to prefer this over tiktok_list_advertisers or tiktok_get_advertiser_info, nor any prerequisites. Usage is inferable but not explicit.

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

Deploy Server