Skip to main content
Glama

Fetch a TikTok sound by ID

tiktok_get_sound
Read-onlyIdempotent

Get a TikTok sound by ID: title, artist, duration, cover image, audio link, whether it is an original sound and how many videos use it. Read-only: returns public data and changes nothing. Costs 1 credit per request.

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": {
      "soundId": "<soundId>"
    },
    "name": "tiktok_get_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
soundIdYesSound ID, the number at the end of the sound URL or a post’s `sound.id`. The sound URL itself works too.
cacheOnlyNoReturn only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.
cacheMaxAgeHoursNoAccept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cacheMaxAgeHours
      Added value: +{
      +  "description": "Accept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / cacheOnly
      Added value: +{
      +  "description": "Return only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.",
      +  "type": "boolean"
      +}
  2. First observed

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, open-world behavior, so "read-only: returns public data and changes nothing" largely restates structured data. However, "Costs 1 credit per request" is genuine behavioral context absent from the annotations and is decision-relevant for an agent managing a credit budget. It stops short of covering failure modes for private, deleted, or region-blocked sounds.

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?

Two sentences: the first front-loads what is returned, the second front-loads the safety and cost profile. No filler, no repetition of the title, and the most decision-relevant facts (read-only, 1 credit) come last where they are easy to scan.

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 no output schema, the description compensates well by listing the concrete return fields, and it discloses the per-request credit cost that an agent needs before calling. For a single-required-parameter read tool with full annotation coverage, the remaining omission (behavior on missing or private sounds) is minor.

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 cache parameters are documented in unusually rich detail in the schema (404 at no cost, cachedAt, live fallback). The description adds nothing about soundId format or the caching trade-off, so it sits at the baseline of 3 where the schema carries the semantic load.

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 a TikTok sound by ID") and enumerates the returned fields (title, artist, duration, cover, audio link, original flag, usage count), which makes the tool's output shape concrete. It does not explicitly distinguish itself from the sibling tiktok_get_sound_videos, so an agent must infer that one returns sound metadata while the other lists videos using it.

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?

Usage is implied rather than stated: an agent can infer this is the lookup for sound metadata, but there is no sentence saying when to call this versus tiktok_get_sound_videos or how to obtain a sound ID. The schema hints at ID sourcing, but the description itself provides no routing guidance or exclusions.

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