Skip to main content
Glama
getmcpads-com

tiktok-ads-mcp-server

by getmcpads-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tiktok get read endpoint

tiktok_get_read_endpoint
Read-onlyIdempotent

Query TikTok Business API read-only JSON endpoints not covered by dedicated tools; validate relative v1.3 paths and query parameters while blocking OAuth, mutations, downloads, and lead records.

Instructions

Advanced GET-only TikTok Business API escape hatch for documented JSON read endpoints not yet modeled by a specialized MCP tool. Relative v1.3 paths and JSON-compatible query parameters are validated; OAuth, mutations, downloads, and lead-record paths are blocked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointYesRelative endpoint such as split_test/result/get, file/video/ad/info, store/list, or business/video/list
parametersNoNative query parameters for this allowlisted read endpoint. Do not provide credentials or account overrides.

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. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / parameters / description
      Added value: +"Native query parameters for this allowlisted read endpoint. Do not provide credentials or account overrides."
    • 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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond that: relative v1.3 path validation, JSON-compatible query parameter validation, and the specific blocked path categories. GET-only fully aligns with the readOnly annotation; no contradiction.

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 dense sentences with zero filler. The purpose is front-loaded ('Advanced GET-only... escape hatch') before constraints, and each clause earns its place — path validation, block categories, and scope are all packed in efficiently.

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 generic escape hatch with an output schema and rich annotations, the description is nearly complete: it covers purpose, scope, validation behavior, and exclusions. The only minor gap is not spelling out what happens on an invalid or non-allowlisted path, which would further guide error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the endpoint parameter carries concrete examples (split_test/result/get, file/video/ad/info, store/list), so the schema does the heavy lifting. The description adds one meaningful constraint beyond the schema — 'JSON-compatible query parameters' — which specifies the accepted format for the parameters object.

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 verb and resource: a GET-only escape hatch for the TikTok Business API's documented JSON read endpoints. It explicitly carves out its niche ('not yet modeled by a specialized MCP tool'), which distinguishes it from the 34 specialized siblings like tiktok_get_ads and tiktok_get_campaigns. No ambiguity about what it is or when it applies.

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 condition 'not yet modeled by a specialized MCP tool' is an explicit when-to-use signal that routes the agent away from siblings, and the blocked categories (OAuth, mutations, downloads, lead-record) define exclusions. However, it stops short of naming concrete alternative tools for those excluded cases, leaving some routing to inference.

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