Skip to main content
Glama
getmcpads-com

tiktok-ads-mcp-server

by getmcpads-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tiktok get entities raw

tiktok_get_entities_raw
Read-onlyIdempotent

Query TikTok campaigns, ad groups, or ads with selected native fields, filters, sorting, and pagination. Use this GET-only escape hatch to access new entity fields before curated schemas update.

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

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to request, starting at 1.
fieldsYesNative provider fields to return. Select only fields supported by the chosen object or report.
pageSizeNoMaximum items requested per page. Follow the returned pagination information for remaining results.
filteringNoNative TikTok filtering object, for example {campaign_ids:["..."]}
orderTypeNoSort direction for the selected ordering field.
entityTypeYesProvider entity type to retrieve.
orderFieldNoProvider field used to order report rows.
advertiserIdYesTikTok advertiser account ID as a string.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. Changed8 schema fields changedv2.0.0
    • addedInput schema / properties / advertiserId / description
      Added value: +"TikTok advertiser account ID as a string."
    • addedInput schema / properties / entityType / description
      Added value: +"Provider entity type to retrieve."
    • addedInput schema / properties / fields / description
      Added value: +"Native provider fields to return. Select only fields supported by the chosen object or report."
    • addedInput schema / properties / orderField / description
      Added value: +"Provider field used to order report rows."
    • addedInput schema / properties / orderType / description
      Added value: +"Sort direction for the selected ordering field."
    • addedInput schema / properties / page / description
      Added value: +"Page number to request, starting at 1."
    • addedInput schema / properties / pageSize / description
      Added value: +"Maximum items requested per page. Follow the returned pagination information for remaining results."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "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."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds context about exposing newly released fields and caller-selected native fields, but does not go beyond that into caveats like invalid field errors or pagination continuation behavior; this is acceptable given annotation coverage but not exceptional.

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, front-loaded with the action and resource, and every clause earns its place. The second sentence justifies the tool's existence as an escape hatch rather than repeating schema information.

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?

For a raw/open-world tool with a full input schema and output schema, the description is sufficiently complete: it states what is listed, the flexible field selection model, and the reason to prefer it over curated endpoints. It could name the curated siblings or caution about field validation, but the schema already carries most of that burden.

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 every parameter already has a meaningful description (e.g. native provider fields, filtering object example, pagination). The description's mention of caller-selected fields, filtering, sorting, and pagination is an accurate summary but adds little per-parameter meaning above the schema.

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 opens with a specific action and resource—listing TikTok campaigns, ad groups, or ads—and immediately distinguishes the tool as a raw GET escape hatch from the MCP's curated schemas. An agent can tell it apart from curated siblings like tiktok_get_campaigns or tiktok_get_ads and understand its broader scope.

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?

The description gives clear context for when the raw tool is appropriate: when newly released native fields are needed before curated schemas catch up. It does not explicitly name the curated alternatives or state when not to use it, so it stops short of a full when/when-not guide.

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

Deploy Server

Other Tools