TikTok Ads by Get MCP Ads

tiktok get spark organic joins

tiktok_get_spark_organic_joins

Read-onlyIdempotent

Joins Spark Ads fields with paid page/post reporting and optional organic identity/post data to inspect ad performance and organic context when permissions allow.

Instructions

Join accessible Spark Ads fields with paid page/post reporting and optional organic identity/post endpoints when permissions allow. Read-only only.

Input Schema

Name	Required	Description
`adIds`	No	Optional ad IDs to inspect.
`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 for page_id reporting. Defaults to today.
`adgroupId`	No	Optional ad group ID filter.
`startDate`	No	Start date YYYY-MM-DD for page_id reporting. Defaults to 14 days ago.
`advertiserId`	Yes	TikTok advertiser ID
`includeOrganicEndpoints`	No	Try identity/post metadata endpoints when Spark IDs are discovered.
`includeExperimentalEndpoints`	No	Also try undocumented/unstable Organic API endpoint candidates that may return 404. Disabled by default to keep warnings actionable.

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

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so 'Read-only only' is largely redundant. The description does add the meaningful caveat that organic identity/post endpoints are permission-gated, which explains partial results — but it says nothing about how failures surface (e.g. warnings) despite the schema flagging 404-prone experimental endpoints.

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 with no padding, and the permission qualifier is placed up front. The phrasing is dense and slightly awkward ('Join accessible Spark Ads fields with paid page/post reporting'), but nothing is wasted.

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 and all 8 params are documented, so the basics are covered. However, for a tool that merges multiple endpoints with experimental fallbacks, the description should explain the merged shape or degraded-result behavior, which it does not.

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 coverage is 100%, so every parameter including includeOrganicEndpoints and includeExperimentalEndpoints is already documented in the schema. The description adds no parameter-level meaning beyond what is structured, so the baseline 3 applies.

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

Purpose3/5

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

The description names Spark Ads fields and paid page/post reporting, but 'Join accessible ... fields with ... reporting' is jargon that never says plainly that it returns a merged reporting dataset. It also doesn't distinguish itself from the sibling tiktok_get_spark_ads, which an agent would reasonably consider first.

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?

'when permissions allow' hints at a precondition but there is no statement of when to pick this over tiktok_get_spark_ads or tiktok_get_report_raw, and no mention of what happens when permissions are missing. Usage is left to inference.

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

Deploy Server