TikTok Ads by Get MCP Ads

tiktok get shop catalog diagnostics

tiktok_get_shop_catalog_diagnostics

Read-onlyIdempotent

Run read-only TikTok Shop catalog diagnostics to check catalog reporting, fall back to Shop auction metrics, and flag endpoint warnings when catalog permissions are missing.

Instructions

Read-only TikTok Shop/catalog/e-commerce diagnostics. Tries catalog reporting first, then Shop auction metrics, and returns endpoint warnings when catalog permissions are unavailable.

Input Schema

Name	Required	Description	Default
`bcId`	No	Optional TikTok Business Center ID. Defaults to TIKTOK_BC_ID/TIKTOK_BUSINESS_CENTER_ID, then advertiser discovery.
`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.
`catalogId`	No	Optional catalog ID for product/product-set inventory endpoint attempts.
`dimension`	No	Reporting dimension used to group and compare results.	product_id
`startDate`	No	Start date YYYY-MM-DD. Defaults to 14 days ago.
`productIds`	No	Optional product IDs to filter report rows where supported.
`advertiserId`	Yes	TikTok advertiser ID
`includeDaily`	No	Add stat_time_day to report dimensions where supported.

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

Behavior4/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 safety is covered. The description adds real context beyond that: the endpoint-fallback strategy and the fact that missing catalog permissions surface as endpoint warnings rather than an error.

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 sentences, front-loaded with the read-only diagnostics scope before the fallback detail. Efficient, with no filler, though the fallback clause is dense enough to blur the primary purpose slightly.

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 explained. However, for a 9-parameter, multi-endpoint hybrid tool, the description leaves unclear what the diagnostics actually measure and when partial results (warnings) versus real data should be expected.

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 in the schema. The description adds no parameter-level meaning (e.g. how catalogId interacts with the fallback path), so the baseline 3 applies.

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 states a specific verb and domain — read-only TikTok Shop/catalog/e-commerce diagnostics — and discloses the fallback chain (catalog reporting first, then Shop auction metrics). It stops short of saying what a 'diagnostic' actually reports, which keeps it from a 5.

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?

It says nothing about when to choose this over siblings such as tiktok_get_insights, tiktok_get_report_raw, or tiktok_get_targeting_catalog, which overlap heavily with catalog/e-commerce reporting. The fallback order is internal behavior, not selection guidance.

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

Deploy Server