TikTok Ads by Get MCP Ads

tiktok get search ads maturity

tiktok_get_search_ads_maturity

Read-onlyIdempotent

Diagnose TikTok Search Ads maturity using keyword and search-term reports plus optional keyword recommendations for read-only account assessment.

Instructions

Diagnose TikTok Search Ads maturity from keyword/search-term reporting and optional keyword recommendation endpoints. Read-only diagnostics only.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`endDate`	No	End date YYYY-MM-DD. Defaults to today.
`dataLevel`	No	TikTok reporting aggregation level. Metrics and dimensions must be compatible with this level.	AUCTION_ADGROUP
`startDate`	No	Start date YYYY-MM-DD. Defaults to 14 days ago.
`advertiserId`	Yes	TikTok advertiser ID
`seedKeywords`	No	Optional seed keywords for keyword recommendation endpoint diagnostics.

Output Schema

Name	Required	Description	Default
`result`	Yes	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.1Oct 30, 2026

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"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so "Read-only diagnostics only" largely restates structured data. The one genuine addition is disclosing which endpoints feed the diagnosis and that the recommendation endpoint is optional, but nothing is said about cost, coverage limits, or what 'maturity' is measured against.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with purpose, no filler. The second sentence is nearly redundant with the readOnlyHint annotation, which is the only small inefficiency.

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?

Output schema exists so return shape need not be described, but the description leaves the core concept opaque: an agent cannot tell what a 'maturity' diagnosis actually yields or how it differs from a plain keyword report. For a six-parameter diagnostic tool this is adequate but thin.

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 every parameter is already documented and the baseline is 3. The description only implicitly links "optional keyword recommendation endpoints" to seedKeywords and adds no format, default, or interaction details (e.g., how startDate/dataLevel affect the diagnosis) beyond the schema.

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?

The description pairs a specific verb ("Diagnose") with a specific resource ("TikTok Search Ads maturity") and names the data sources used — keyword/search-term reporting plus optional keyword recommendation endpoints. It is clear what the tool does, though it never contrasts itself with near-neighbours like tiktok_search_keywords or tiktok_get_insights, so an agent must infer the boundary.

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?

"Read-only diagnostics only" gives a soft usage constraint (diagnostic, not reporting/pulling raw data), but there is no explicit when-to-use / when-not-to-use guidance and no named alternative among the many sibling reporting tools. The context is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server