Skip to main content
Glama
Sign In
soclip-mcp

soclip-mcp

by huangyunbin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_video_media

Extract direct video download links and metadata—including title, author, duration, and thumbnail—from TikTok, Instagram, X/Twitter, and Facebook URLs.

Instructions

Extract video media direct links and metadata from social video URLs (supports TikTok, Instagram, X/Twitter and Facebook). Costs 2 credits.

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": "get_video_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe social video URL (TikTok, Instagram, X/Twitter or Facebook)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the 2-credit cost, which is genuinely useful context an agent cannot get from the schema and which pairs with the get_balance sibling. It says nothing about failure modes, whether invalid URLs still consume credits, or rate limits.

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 short sentences, capability front-loaded and the cost constraint appended. Every clause carries information; nothing is padded.

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?

For a one-parameter, no-output-schema tool, the description conveys the operation, supported inputs, and cost, which is most of what an agent needs. The remaining gap is return-shape and error behavior, minor given the low complexity.

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?

There is one parameter at 100% schema coverage, so the schema already documents the url field and its accepted platforms. The description's platform list duplicates rather than extends that, adding no syntax or format guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (extract) and resource (video media direct links plus metadata) scoped to named platforms (TikTok, Instagram, X/Twitter, Facebook). The only sibling, get_balance, is an unrelated credit-check tool, so there is no ambiguity to resolve.

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 supported-URL framing implies when to call it, but there is no explicit when-not guidance, no prerequisites, and no mention of what to do with unsupported platforms or failed extraction. With a single sibling and no alternatives, implied usage is the minimum viable bar.

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