TikTok Ads by Get MCP Ads

tiktok get events

tiktok_get_events

Read-onlyIdempotent

Discover TikTok pixel and app events or tracking diagnostics for an advertiser, using endpoint checks with reporting-dimension fallback when direct data is unavailable.

Instructions

Discover pixel/app events or accessible tracking diagnostics for an advertiser. Uses best-effort endpoint checks plus reporting dimensions as fallback.

Input Schema

Name	Required	Description
`bcId`	No	Optional Business Center ID. Defaults to TIKTOK_BC_ID/TIKTOK_BUSINESS_CENTER_ID for BC pixel discovery.
`appId`	No	Optional TikTok app ID for app event lookup when the endpoint is available.
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`endDate`	No	End date YYYY-MM-DD for tracking diagnostics. Defaults to today.
`pixelId`	No	Optional pixel ID for pixel event lookup.
`startDate`	No	Start date YYYY-MM-DD for tracking diagnostics. Defaults to 7 days ago.
`advertiserId`	Yes	TikTok advertiser ID

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

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful caveat that results are best-effort and may be synthesized from reporting dimensions, but it is phrased in jargon and never says what that means for the caller (e.g. partial or approximate data, empty results when an endpoint is unavailable).

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

Conciseness4/5

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

Two sentences, no filler, with the dual purpose front-loaded before the implementation caveat. Slightly penalized because the second sentence is compression-heavy jargon that trades clarity for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 full parameter documentation, the return shape and inputs are covered elsewhere. What is missing is guidance on the two discovery paths (pixel vs app vs diagnostics), which is the main decision an agent faces with this 7-parameter tool.

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% across all 7 parameters, including pixelId, appId, bcId, and the date range, so the schema carries the semantic load. The description mentions neither which parameters select which mode nor any interaction between them, so it adds nothing on top of a fully documented schema — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names a verb ('Discover') and resources ('pixel/app events', 'tracking diagnostics'), but bundles two loosely related capabilities into one tool without clarifying which mode applies. It also fails to distinguish itself from close siblings like tiktok_get_pixels, so an agent cannot tell from the description alone which to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no exclusions, and no named alternative. The clause about 'best-effort endpoint checks plus reporting dimensions as fallback' describes internal behavior rather than telling the agent when this tool is the right choice over tiktok_get_pixels or tiktok_get_audience_report.

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

Deploy Server