Skip to main content
Glama
Sign In

Socify-mcp

by com.trysocify
OverviewDiscussionsAdmin

tiktok_music/info

Fetch music/audio metadata by music id (music.id from a video lookup).. Platform=tiktok resource=music/info. Costs 1 credit(s) per request. Requires Authorization: Bearer <api_key>.

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": "tiktok_music/info"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMusic id (music.id from a video lookup).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / examples
      Previous value: -[
-  "7703604097215171361"
-]New value: +[
+  "7128005345142425601"
+]
  2. Added

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the billing cost (1 credit per request) and the required Authorization: Bearer header, but says nothing about rate limits, error behavior, or what metadata is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the text contains a doubled period typo and boilerplate 'Platform=... resource=...' metadata that duplicates the tool name. The content is short, yet not every clause earns its place.

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?

For a single-parameter lookup with no output schema, the definition covers auth and cost, which is the essential operational context. It is only marginally complete because an agent cannot infer the shape or fields of the returned music metadata.

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 coverage is 100% and the single id parameter is already documented in the schema with an example. The description only restates the id's provenance, adding no format or syntax detail beyond the schema baseline.

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: fetching music/audio metadata by music id. It is distinguishable from data-listing siblings like tiktok_music_videos, though it never explicitly contrasts with them, which keeps it short of 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?

The parenthetical '(music.id from a video lookup)' implies the id should be sourced from a video lookup step, which is mild workflow guidance. There is no explicit when-to-use/when-not statement or named alternative sibling.

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

All Socify-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