Skip to main content
Glama
Sign In

socialbridge-mcp

by io.github.IsaiahDupree
OverviewDiscussionsAdmin

YouTube transcript / caption languages

youtube_transcript
Read-onlyIdempotent

Available caption-language list (and cue segments where retrievable) for a YouTube video. Provide url OR videoId. Keyless. NOTE: actual cue text is BotGuard-gated keyless, so it is reported honestly (available:false, empty segments) rather than fabricated.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoYouTube watch URL. Provide url OR videoId.
langNoPreferred caption language (BCP-47, e.g. "en").
videoIdNo11-char video id. Provide url OR videoId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses a critical behavioral trait beyond annotations: actual cue text is BotGuard-gated keyless, and the tool reports 'available:false' or empty segments rather than fabricating data. This adds important context about reliability and honesty, exceeding what readOnlyHint and idempotentHint already convey.

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?

The description is two sentences, front-loaded with the core purpose, followed by usage and a concise limitation note. Every word earns its place, with no redundancy or extraneous information.

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?

Given only three optional parameters and no output schema, the description adequately explains what the tool returns (caption-language list and cue segments where retrievable) and how it behaves when not retrievable (available:false, empty segments). This covers the essential information for correct selection and use.

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% with descriptions for all three parameters. The description's 'Provide url OR videoId' adds exclusivity that is also already stated in the schema's parameter descriptions, so it does not significantly enhance parameter understanding beyond the schema.

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?

The description clearly states the tool returns available caption-language list and cue segments for a YouTube video, specifying the resource (YouTube video) and scope (caption languages). It is distinct from sibling tools, which are all social media related, so there is no ambiguity about what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage instruction 'Provide url OR videoId' and notes the keyless access, giving clear context on how to invoke it. It does not explicitly mention alternatives, but the sibling tools are unrelated (social media), so the intended use case is implied and unambiguous.

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

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