Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok song

tiktok_song_get
Read-onlyIdempotent

Retrieve details for a TikTok song or sound by its ID to identify audio and inspect metadata.

Instructions

Get details for a TikTok song or sound by id. Requires id.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_song_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTikTok song or sound id. Use the trailing id from a music page URL, or `music.id` from a video lookup.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds no behavioral context beyond restating that `id` is required, which the schema already enforces as mandatory. Nothing about the return shape, error behavior, or data freshness is offered.

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, front-loaded with the action and resource. The second sentence is largely redundant with the schema's required-field declaration, which is the only small waste.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read tool with rich annotations and fully documented parameters, so the definition is close to complete. However, with no output schema, the description does not say what "details" actually comprise (audio URL, duration, author, usage counts), which is the one piece an agent cannot get elsewhere.

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%, including detailed notes on where to obtain the id and the special handling of llm_model and conversation_id, so the baseline of 3 applies. The description's "Requires `id`" repeats a requirement the schema already marks as required and adds no new meaning.

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 details for a TikTok song or sound by id") that is clearly distinguishable from siblings like tiktok_music_videos_list or tiktok_video_get. It stops short of explicitly naming the sibling it complements, so it lands at a solid 4 rather than 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?

Usage is only implied: fetch song details given an id, with the id sourcing guidance living in the schema rather than the description. There is no statement of when to prefer this over tiktok_music_videos_list or how it relates to video lookups, leaving the agent to infer the routing.

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

Deploy Server

Other Tools