TikTok Ads by Get MCP Ads

tiktok get creative fatigue recipes

tiktok_get_creative_fatigue_recipes

Read-onlyIdempotent

Identify likely creative fatigue patterns in ad-level daily reporting and return read-only refresh recipes; no creative creation, editing, or uploads.

Instructions

Find likely creative fatigue patterns from ad-level daily reporting and return read-only refresh recipes. Does not create, edit, or upload creatives.

Input Schema

Name	Required	Description
`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.
`startDate`	No	Start date YYYY-MM-DD. Defaults to 14 days ago.
`advertiserId`	Yes	TikTok advertiser ID
`minImpressions`	No	Minimum reported impressions required for a row to enter the analysis.
`declineThresholdPct`	No	Percentage decline used as a candidate signal for creative fatigue, requiring further evidence.

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.

Changed3 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / minImpressions / maximum
```
Added value: +9007199254740991
```

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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the read-only claim largely restates structured data. The description does add real context that the output is derived from ad-level daily reporting and framed as candidate signals rather than verdicts, but says nothing about analysis cost, data freshness, or how sparse data is handled.

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 tight sentences: the core action first, the read-only boundary second. Nothing is padding and nothing is buried.

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 present, return values need not be described, and annotations cover the safety profile, so the description is nearly sufficient. It could still hint at the default 14-day window or that results are capped by limit, but those are already in the schema.

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 including declineThresholdPct and minImpressions is already documented with defaults and bounds. The description adds no parameter-level meaning beyond what the schema provides, which is the expected baseline of 3 when the schema carries the load.

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 analytic resource: find likely creative fatigue patterns from ad-level daily reporting and return refresh recipes. The scope is narrow enough that an agent can distinguish it from generic reporting siblings like tiktok_get_insights or tiktok_get_report_raw, and the closing clause explicitly rules out creative mutation.

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 gives a useful negative boundary ('does not create, edit, or upload creatives') but never says when to prefer this over tiktok_get_insights or tiktok_get_report_raw for plain performance data, nor any prerequisites beyond the advertiser ID. Usage is implied by the topic rather than routed explicitly.

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

Deploy Server