TikTok Ads by Get MCP Ads

tiktok get carousel music

tiktok_get_carousel_music

Read-onlyIdempotent

Retrieve TikTok music recommendations for uploaded images in a standard image ad or carousel, verifying each image is carousel-usable before you select a music_id for approval.

Instructions

Get TikTok music recommendations for exactly the uploaded images in a standard, non-catalog image ad (one card) or carousel. Verifies each image is carousel-usable. Read-only; select a returned music_id in the approval preview and use the same images in the ad. Music is for use on TikTok only.

Input Schema

Name	Required	Description	Default
`imageIds`	Yes	Ordered list of 1-35 distinct uploaded image IDs owned by this advertiser. Use the exact same images in the approved carousel.
`advertiserId`	Yes	Exact TikTok numeric ID as a string, never a rounded JavaScript number.

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds value beyond them: it discloses that each image is validated for carousel usability (a failure mode the agent should anticipate) and that returned music is licensed for TikTok use only. It does not cover error behavior or rate limits, but the added context is substantive.

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?

Four compact sentences, front-loaded with purpose, then validation behavior, then workflow and licensing caveat. Every sentence carries information; the only mild redundancy is restating the image-matching constraint twice.

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?

An output schema exists so return values need no explanation, and the description still covers the pieces an agent needs: input scope, input verification behavior, downstream selection of music_id, and the TikTok-only usage restriction. Complete for a two-parameter read tool.

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 both parameters are fully documented with types, limits (1-35 distinct images), and the advertiser ID format. The description only reinforces the 'use the exact same images' constraint, adding no syntax or format detail beyond the schema — baseline 3 is appropriate.

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?

States a specific verb and resource ('Get TikTok music recommendations') plus a precise scope qualifier: 'exactly the uploaded images in a standard, non-catalog image ad (one card) or carousel.' That level of scope detail distinguishes it from generic asset/creative siblings, though it never names an alternative tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context is given (standard non-catalog image ad, one card or carousel) and the downstream workflow is spelled out ('select a returned music_id in the approval preview and use the same images in the ad'). The 'non-catalog' qualifier acts as an implicit exclusion, but no explicit when-not-to-use or alternative-tool guidance is offered.

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

Deploy Server