Skip to main content
Glama

Caelara Labs Social Analytics

youtube_metadata

YouTube video metadata via public oEmbed + thumbnail URLs

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

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video URL or id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. 'Public oEmbed' weakly implies no authentication is required, which is useful, but the description never says what fields come back, what happens on an invalid or private video, or whether the call can fail. For a zero-annotation tool this leaves most behavioral questions unanswered.

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?

A single compact fragment with zero wasted words, and the key facts (source and return type) are front-loaded. It is under-specified rather than bloated, but the missing verb slightly hurts scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-parameter tool, but with no output schema and no annotations, the description should state which metadata fields the oEmbed response yields (title, author, thumbnail) so the agent knows what it gets back. That gap is significant for a tool whose entire value is its return payload.

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 a single required parameter with 100% schema description coverage ('YouTube video URL or id'), so the schema already does the work. The description adds nothing about accepted URL formats (watch, shorts, youtu.be) or bare-id handling, so the baseline 3 applies.

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

Purpose3/5

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

The description names a specific resource (YouTube video metadata) and the mechanism (public oEmbed + thumbnail URLs), which distinguishes it from siblings like thumbnail_analyzer or tiktok_oembed. However, it is a noun phrase with no verb, so the agent must infer that this is a fetch/retrieve operation rather than, say, a validator or parser.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance whatsoever. Nothing tells the agent to prefer tiktok_oembed for TikTok URLs, or to use thumbnail_analyzer if it needs actual image analysis rather than thumbnail URLs. The agent must infer selection from the platform name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources