TikTok Ads by Get MCP Ads

tiktok get entities raw

tiktok_get_entities_raw

Read-onlyIdempotent

List TikTok campaigns, ad groups, or ads with selected native fields, filtering, sorting, and pagination. Use it as a GET-only escape hatch to expose newly released fields without curated schemas.

Instructions

List TikTok campaigns, ad groups, or ads with caller-selected native fields, filtering, sorting, and pagination. This GET-only escape hatch exposes newly released entity fields without waiting for the MCP's curated schemas.

Input Schema

Name	Required	Description
`page`	No	Page number to request, starting at 1.
`fields`	Yes	Native provider fields to return. Select only fields supported by the chosen object or report.
`pageSize`	No	Maximum items requested per page. Follow the returned pagination information for remaining results.
`filtering`	No	Native TikTok filtering object, for example {campaign_ids:["..."]}
`orderType`	No	Sort direction for the selected ordering field.
`entityType`	Yes	Provider entity type to retrieve.
`orderField`	No	Provider field used to order report rows.
`advertiserId`	Yes	TikTok advertiser account ID as a string.

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.

Changed8 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / filtering / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / orderField / $ref
```
Removed value: -"#/properties/fields/items"
```
addedInput schema / properties / orderField / maxLength
```
Added value: +120
```
addedInput schema / properties / orderField / minLength
```
Added value: +1
```
addedInput schema / properties / orderField / pattern
```
Added value: +"^[A-Za-z][A-Za-z0-9_]*$"
```
addedInput schema / properties / orderField / type
```
Added value: +"string"
```

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.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, destructiveHint, so the safety profile is fully covered. The description adds the rationale for the tool's existence (uncurated fields, pass-through to the provider) but says nothing extra about rate limits, field-validation failure behavior, or how pageSize interacts with the returned pagination.

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 sentences, zero filler. The primary action is front-loaded and the 'escape hatch' qualifier follows immediately as supporting context.

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?

Output schema exists, annotations cover safety and world-model semantics, and the schema fully documents all eight parameters including the free-form nested filtering object. The description supplies the only thing structured fields can't: why this raw endpoint exists alongside the curated ones.

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%, so every parameter including the nested filtering object and the entityType/orderType enums is already documented in the schema — baseline 3 applies. The description's phrasing ('caller-selected native fields', 'filtering, sorting, pagination') only restates which parameter families exist, adding no format or constraint detail beyond the schema.

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 and resource ('List TikTok campaigns, ad groups, or ads') plus the distinguishing capability set (native fields, filtering, sorting, pagination). It does not name the overlapping curated siblings (tiktok_get_campaigns, tiktok_get_adgroups, tiktok_get_ads), so the differentiator is only implicit.

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?

'Escape hatch exposes newly released entity fields without waiting for the MCP's curated schemas' implies the when-to-use case (need fields the curated tools don't yet expose). It never states the inverse — 'use tiktok_get_campaigns instead when a curated schema exists' — nor names which sibling to prefer.

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

Deploy Server