Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_social_youtube_metadata

Fetches YouTube video metadata and thumbnail URLs from a video link or ID via public oEmbed, so you can enrich posts, previews, or analytics without scraping.

Instructions

[Social Analytics] YouTube video metadata via public oEmbed + thumbnail URLs Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://social.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video URL or id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does disclose useful behavior: it is a public (unauthenticated) lookup, the data provenance is oEmbed plus thumbnail URLs, and it reports p50 12 ms / p95 14 ms with a benchmark date, which helps an agent judge suitability for latency-sensitive paths. Gaps remain around rate limits, error/failure behavior for private or removed videos, and which metadata fields come back.

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 compact sentences, front-loaded with the capability statement before the performance detail. The benchmark timestamp and domain URL are somewhat promotional but do carry planning value for an agent, and nothing is redundant.

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 read tool this is close to sufficient, but with no output schema the description never indicates what 'metadata' includes (title, author, thumbnail dimensions), forcing the agent to call blind to learn the payload shape. A one-clause return-value summary would close the gap.

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?

Only one parameter and schema coverage is 100%, with the schema itself stating 'YouTube video URL or id'. The description adds no format examples (e.g., watch?v=, youtu.be, bare 11-character id) beyond the schema, so it sits at the baseline for fully covered parameters.

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?

Names the resource (YouTube video metadata) and the technique/source (public oEmbed + thumbnail URLs), so an agent knows exactly what it retrieves. It does not distinguish itself from neighbors like caelara_social_tiktok_oembed or caelara_social_thumbnail_analyzer, so platform differentiation is left to the name.

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 phrase 'public oEmbed' implicitly scopes usage to publicly available videos and suggests a lightweight lookup rather than deep analysis, but there is no explicit when-to-use, when-not-to-use, or routing to sibling tools. Guidance is inferable rather than stated.

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