Skip to main content
Glama
getmcpads-com

tiktok-ads-mcp-server

by getmcpads-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tiktok get targeting catalog

tiktok_get_targeting_catalog
Read-onlyIdempotent

Read TikTok Ads targeting and planning catalogs for locations, interests, hashtags, keywords, devices, carriers, and time zones. Pass a catalog name and optional query to find valid targeting options.

Instructions

Read TikTok targeting and planning catalogs: locations, languages, interests, behaviors, hashtags, Search Ads keyword ideas/health, devices, carriers, contextual tags, content exclusions, and time zones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch text used to find matching entries in the selected catalogue.
catalogYesAllowlisted targeting dictionary or catalog to inspect.
parametersNoAdditional native parameters documented for the selected GET endpoint
advertiserIdNoTikTok 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. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / advertiserId / description
      Added value: +"TikTok advertiser account ID as a string."
    • addedInput schema / properties / catalog / description
      Added value: +"Allowlisted targeting dictionary or catalog to inspect."
    • addedInput schema / properties / query / description
      Added value: +"Search text used to find matching entries in the selected catalogue."
    • 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

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful functional scope by listing the catalog categories, but it does not describe return format, pagination, rate limits, or whether certain catalogs may be unavailable for some advertisers. This parallels the benchmark case where the description contributes context but no behavioral depth beyond safety annotations.

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?

The description is a single front-loaded sentence with no wasted words. The leading verb and resource are clear, and the following colon-led list is informative without being excessive. Every part of the sentence contributes to understanding.

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?

While the tool is read-only with a rich schema and output schema, the description does not explain how to choose between the `catalog` parameter and the free-form `parameters` object, nor does it mention that some catalogs may require `advertiserId` or `query`. Given the nested objects and 17 enum values, the description alone is too sparse for fully confident invocation, though annotations and schema partially compensate.

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 the baseline is 3. The description does not elaborate on any parameters, such as how `query` or `parameters` interact with a chosen `catalog`. It provides no additional meaning beyond what the schema already documents.

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 uses the specific verb "Read" plus a clear resource (“targeting and planning catalogs”) and enumerates the catalog contents (locations, languages, interests, behaviors, hashtags, etc.). This is distinctive enough to separate it from sibling tools like tiktok_get_targeting or tiktok_search_keywords, since it focuses on dictionary/catalog data rather than account or campaign records.

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?

The description implies that this tool is used when an agent needs to inspect or validate targeting catalog values, but it never explicitly states when to choose this tool over alternatives such as tiktok_get_targeting or tiktok_search_keywords. There are no when/when-not conditions or references to sibling tools, so the guidance is only implicit.

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