Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

tiktok_mobile_music_posts

Read-only

List TikTok videos using one sound. Supply a music_id returned by a sound search or chart; count is accepted for compatibility but TikTok currently chooses its own page size, so continue with cursor. sort is fresh (newest, default) or popular.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "music_id": "<music_id>"
    },
    "name": "tiktok_mobile_music_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoListing: fresh (newest, default) or popular (requires the device-backed signer).
countNoAccepted for app compatibility; TikTok currently uses its own page size.
cursorNoPagination cursor returned by the previous page.
music_idYesTikTok sound ID returned by a music search or chart.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "Listing: fresh (newest, default) or popular (requires the device-backed signer).",
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context: count is a no-op because TikTok picks its own page size, so the caller must loop on cursor. It doesn't discuss error or rate-limit behavior, but with annotations and an output schema present this is good coverage.

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?

Three tight sentences, all front-loaded: purpose first, then the required input's provenance, then the pagination caveat and sort values. Nothing is repeated for filler and every clause carries information an agent needs before calling.

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?

With an output schema covering return shape and annotations covering read-only/open-world behavior, the description only needs to cover usage and quirks, which it does. The one gap is that the 'popular requires the device-backed signer' constraint appears only in the schema, not in the description.

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% and the description largely restates it: count being accepted for compatibility, cursor being the pagination handle, sort's fresh/popular split. 'Continue with cursor' adds a little operational direction, but most of the semantic load is already carried by the schema.

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 and resource ('List TikTok videos using one sound') and scopes the input ('Supply a music_id returned by a sound search or chart'). That cleanly separates it from sibling sound tools like tiktok_mobile_music_related, tiktok_mobile_music_trending, and tiktok_mobile_search_music without opening any schema.

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?

Gives the prerequisite for the required parameter (music_id must come from a sound search or chart) and tells the caller how to paginate ('continue with cursor') rather than relying on count. It doesn't explicitly say when to prefer a sibling tool over this one, which keeps it at 4.

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

All Crawlora MCP toolsInspect
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