Skip to main content
Glama
getmcpads-com

tiktok-ads-mcp-server

by getmcpads-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tiktok search keywords

tiktok_search_keywords
Read-onlyIdempotent

Get keyword suggestions for TikTok Search Ads. Returns recommended keywords with search volume estimates.

Instructions

Get keyword suggestions for TikTok Search Ads. Returns recommended keywords with search volume estimates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
keywordsYesSeed keywords to get suggestions for
advertiserIdYesTikTok advertiser ID

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 / limit / description
      Added value: +"Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional 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

A3.8/5.0
Behavior3/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 agent knows it is a safe read operation. The description adds that it returns recommended keywords with volume estimates, which is useful but not extensive. There is no contradiction, and the annotation coverage means the description doesn't need to carry the full burden.

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 with no redundancy. The purpose is front-loaded, and the return detail is stated succinctly. Every word 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 a rich annotation set covering safety and idempotency, a complete parameter schema, and an output schema (has_output_schema=true), the description covers the core purpose and return shape. It doesn't mention any prerequisites or caveats, but given the overall context, nothing critical is missing.

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 all three parameters (advertiserId, keywords, limit) are already documented in the schema. The description adds no extra parameter-level semantics beyond what the schema provides, so a 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?

The description states a specific verb (get), resource (keyword suggestions), and context (TikTok Search Ads), plus the return value (keywords with search volume estimates). It is unambiguous and distinct from the many sibling tools, which are all about audiences, ads, campaigns, or reports.

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 this is for generating keyword suggestions but does not explicitly state when to prefer it over alternatives or when not to use it. No exclusions or alternative tool references are given, leaving the agent to infer the context from the tool name and description.

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