Influship

List TikTok sound videos

list_tiktok_music_videos

Read-only

Fetch one page of videos using a sound clip music_id. Continue with next_cursor and the same music_id; cursors are opaque. Duplicate results are preserved. Media links are temporary. Each successful page, including an empty page, costs 0.2 account credits.

Input Schema

Name	Required	Description	Default
`cursor`	No
`music_id`	Yes	TikTok sound clip ID, not a recording or album ID

Output Schema

Name	Required	Description	Default
`ok`	No
`data`	No
`count`	No
`results`	No
`has_more`	No
`not_found`	No
`next_cursor`	No
`suggested_followups`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 23, 2026

addedInput schema / $ref

Added value: +"#/definitions/TikTokMusicVideosRequest"

addedInput schema / definitions

Added value: +{
+  "TikTokMusicVideosRequest": {
+    "properties": {
+      "cursor": {
+        "maxLength": 2048,
+        "minLength": 1,
+        "type": "string"
+      },
+      "music_id": {
+        "description": "TikTok sound clip ID, not a recording or album ID",
+        "pattern": "^[1-9][0-9]{0,24}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "music_id"
+    ],
+    "type": "object"
+  }
+}

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

AddedSep 8, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Adds substantial context beyond the readOnly/openWorld annotations: credits cost (0.2 per successful page, including empty pages), duplicate preservation, temporary media links, and opaque cursors. These are non-obvious behavioral traits an agent needs before invoking.

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?

Every sentence carries distinct, needed information – pagination, duplicates, temp links, cost – with no filler. Information is front-loaded with the primary operation first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 needn't be described. The description covers pagination mechanics, cost, duplicate handling, and link volatility, leaving nothing essential for correct invocation missing.

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?

The music_id schema description already clarifies it's a sound clip ID; the description reinforces this and explains the cursor's continuation role and opacity. One weakness: it references 'next_cursor' while the actual request parameter is named 'cursor', which could mildly confuse the agent.

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 ('Fetch one page of videos') and resource ('using a sound clip music_id'), making the operation and scope clear. It doesn't explicitly name sibling tools (e.g., search_tiktok_videos or list_tiktok_hashtag_videos) to differentiate itself, keeping it just below 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 Guidelines3/5

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

It explains how to continue pagination ('next_cursor and the same music_id') but gives no explicit guidance on when to choose this tool over related siblings like search_tiktok_videos or get_tiktok_music. Usage is implied rather than contrasted.

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

All Influship 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.