Skip to main content
Glama

TokConnect: TikTok Research

One sound

sound
Read-onlyIdempotent

One TikTok sound (id = sound id from any post or sound_search, or a sound link): detail or the videos using it. Example: {"id":"7012...","method":"videos"}.

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": {
      "id": "<id>"
    },
    "name": "sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSound id (sound.id on a post) or a TikTok sound link.
limitNoResults per page. Max 50. Values above a method's maximum are lowered and reported in notes.
cursorNoPaging: pass the next value from the previous response unchanged. Omit on the first page.
detailNocompact (default) returns the useful fields; full adds the full raw record (large).compact
methodNoWhat to get. detail: title, author, duration, original or licensed, post count | videos: videos using the sounddetail

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / detail / description
      Previous value: -"compact (default) returns the useful fields; full adds the raw upstream payload (large)."New value: +"compact (default) returns the useful fields; full adds the full raw record (large)."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the accepted id formats and a concrete invocation example, but says nothing about pagination behavior or the notes mechanism that the schema mentions for clamped limits.

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 plus a minimal example, with the id sourcing rule front-loaded. The telegraphic phrasing costs a little readability but nothing is wasted.

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 present, return values need not be described, and all five parameters are fully documented in the schema. What remains missing is minor: no guidance on paging through many videos or on the relationship between limit and the method-specific maximum.

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 the schema already explains id, limit, cursor, detail and method. The description's example clarifies how id and method combine in practice, but adds no semantics the schema does not already carry; baseline 3 applies.

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?

Names a specific resource (one TikTok sound) and the two modes it supports (detail or videos using it), and points at sound_search as the id source, which separates it from the search sibling. The verb is elliptical ("detail or the videos using it"), so the operation has to be inferred, but the intent is unmistakable.

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?

Implies the precondition (you must already have a sound id or link) and tells you sound_search is how ids are found, plus that method selects detail vs videos. There is no explicit when-not or statement of what the tool returns versus the search tool, so routing is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources