Skip to main content
Glama
Sign In
TikTok Ads by Get MCP Ads

TikTok Ads by Get MCP Ads

by get-mcp-ads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tiktok search keywords

tiktok_search_keywords
Read-onlyIdempotent

Retrieve keyword suggestions for TikTok Search Ads and view estimated search volumes to identify relevant terms for ad campaigns.

Instructions

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

Input 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

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.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful detail that results are suggestions with search volume estimates, but says nothing about how the seed keywords are expanded or how many suggestions per seed.

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 short sentences, purpose and return payload front-loaded, zero filler. Nothing to cut.

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?

An output schema exists, so return values need not be described, and annotations cover safety. What's missing is how seed keywords drive the results and any usage framing, which matters for an agent deciding when to call this instead of a reporting tool.

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 advertiserId, keywords and limit are already documented in the schema. The description only implies that the keywords parameter acts as seeds; it adds no format, count, or matching guidance beyond structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get keyword suggestions for TikTok Search Ads") plus the return content ("recommended keywords with search volume estimates"). No sibling tool covers keyword research, so the tool is implicitly distinguishable, though the description never names that contrast.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative guidance is given; the Search Ads context is the only usage signal. An agent must infer that this belongs in a keyword-research/planning step rather than reporting, and nothing explains prerequisites like needing a valid advertiserId.

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