Socify-mcp

tiktok_videos/info

Fetch public details for a single TikTok video by full video URL.. Platform=tiktok resource=videos/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": {
      "url": "<url>"
    },
    "name": "tiktok_videos/info"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Full TikTok video URL.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedInput schema / properties / url / examples

Previous value: -[
-  "https://www.tiktok.com/@daviddobrik/video/7165262254722534698"
-]New value: +[
+  "https://www.tiktok.com/@mrbeast/video/7679839713573784863"
+]

AddedNov 3, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does add genuinely useful operational context that structured fields don't provide: 1 credit per request and the required Authorization bearer header. It omits what "public details" actually contains, what happens on a malformed or private URL, and any rate-limit behavior.

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?

The definition is short and front-loads the core purpose, with cost and auth as supporting sentences. It loses a point for a stray double period ("URL..") and for the terse "Platform=tiktok resource=videos/info" token, which reads as metadata noise but at least costs little space.

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 one-parameter read tool this is close to sufficient: purpose, cost, and auth are all stated. However, with no output schema and no annotations, the description should say what the returned "details" include and whether non-public or invalid URLs error out; that gap is the main incompleteness.

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 url parameter already has a description and an example, so the schema does the work. The description only restates "full video URL" without adding format constraints (e.g., whether short links or share URLs are accepted). 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?

"Fetch public details for a single TikTok video by full video URL" names a specific verb (fetch), resource (TikTok video details), and scope (single, by URL). It is clearly distinguishable from tiktok_videos/comments and tiktok_profile/videos by the name and the word "single," though it never names a sibling explicitly.

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: the phrase "by full video URL" tells the agent what input shape selects this tool, and "single" hints it is not a listing operation. There is no explicit statement of when to prefer this over tiktok_videos/comments or the profile endpoints, and no prerequisites or failure conditions.

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

All Socify-mcp tools Inspect

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

Need Help?