AdsAgent — TikTok Ads MCP

List tenant products

products_list

Read-only

List TikTok-owned product cards for the current user. Product card identity is shared with the Meta channel: the same card appears with the same identity in both.

REQUIRED: none. Optional: limit (1..50, default 20), cursor (next_cursor from the previous page; keep limit/expand identical), expand (list of matching_rules, mmp_matches — heavy fields omitted by default). Only TikTok-owned cards are returned; each carries product_ref (use it in the other product tools) and never the internal id. EXAMPLE: products_list({"limit": 20})

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`expand`	No
`connection_context`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 17, 2026

removedInput schema / properties / channel_pid

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Channel Pid"
-}

addedInput schema / properties / cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Cursor"
+}

addedInput schema / properties / expand

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "enum": [
+          "matching_rules",
+          "mmp_matches"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Expand"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 20,
+  "maximum": 50,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}

Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```
First observedSep 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only/non-destructive/local-only, and the description adds genuinely useful behavior: only TikTok-owned cards are returned, identity is shared with the Meta channel, product_ref (not internal id) is exposed, and heavy expand fields are omitted by default. It stops short of describing ordering or empty-result behavior.

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?

Front-loads purpose, then REQUIRED/Optional params, then a return-shape note, then a concrete example call. Dense but every line earns its place with no redundant restatement of the tool name.

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?

For a 4-param read tool with no output schema, the description supplies the essential return semantics (product_ref vs internal id, TikTok-only scope) and pagination contract. The unexplained connection_context pattern and absent output schema are the only minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description carries the load and does so well: it documents limit's 1..50 range and default 20, explains cursor must come from the prior next_cursor with limit/expand held constant, and lists valid expand values with their cost. Only connection_context is left undocumented.

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+resource ('List TikTok-owned product cards for the current user') and clarifies the cross-channel identity model. This clearly separates it from siblings like products_get_actions and products_get_top_campaigns, which operate on derived data rather than the card list itself.

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?

Usage is implied (paginate, then reuse product_ref in other product tools) and it hints downstream usage, but it never names an alternative or states when NOT to use this tool. No explicit routing versus the other product_* siblings.

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

All AdsAgent — TikTok Ads MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?