Skip to main content
Glama
Sign In
get-mcp-ads

TikTok Ads by Get MCP Ads

by get-mcp-ads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tiktok get read endpoint

tiktok_get_read_endpoint
Read-onlyIdempotent

Query documented TikTok Business API GET endpoints not covered by specialized tools, validating relative v1.3 paths and JSON query params 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

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

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. Changed3 schema fields changedv2.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / parameters / propertyNames
      Added value: +{
+  "type": "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"
+  }
+]
  2. First observedv2.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantive behavior beyond the readOnly/idempotent annotations: relative v1.3 path validation, JSON-compatible parameter validation, and explicit blocking of OAuth, mutations, downloads, and lead-record paths. It does not specify what validation errors look like or how authentication is supplied, which keeps it short of a 5 even with an output schema present.

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, front-loading the escape-hatch purpose before the validation and exclusion rules. Every clause earns its place.

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, rich annotations, and fully described parameters, the description covers what an agent needs to decide to call this and how to shape inputs. It could clarify what 'documented' means and how blocked/validation failures surface, but the essentials are complete.

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 both endpoint and parameters are already documented with examples and the no-credentials constraint. The description only adds the v1.3 relative-path and JSON-compatibility notes, which is marginal value over the schema — baseline 3 is appropriate.

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 documented JSON read endpoints not yet modeled by a specialized MCP tool. The phrase 'not yet modeled by a specialized MCP tool' immediately distinguishes it from every specialized sibling like tiktok_get_campaigns or tiktok_get_insights.

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

Usage Guidelines5/5

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

Explicitly scopes when to use it (unmodeled documented JSON read endpoints) and when not to use it (OAuth, mutations, downloads, lead-record paths are blocked). It also implies the alternative class — specialized MCP tools — for endpoints that are already modeled.

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