Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

youtube_get_video

Read-onlyIdempotent

Retrieve metadata, statistics, and content details for a YouTube video by video ID to support analysis, reporting, or agent workflows.

Instructions

Get metadata, statistics, and content details for a YouTube video.

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": {
      "api_key": "<api_key>",
      "video_id": "<video_id>"
    },
    "name": "youtube_get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYes
video_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is fully covered before reading the description. The description adds a light behavioral signal by enumerating the categories of returned data (metadata, statistics, content details), but says nothing about what happens with an unknown/deleted/private video or quota/rate behavior for a live external API.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes partly at the cost of the missing detail noted elsewhere.

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 2-parameter tool with no output schema and fully undocumented params, the description should specify the video_id format and what the returned payload contains. It gestures at return content ('statistics, content details') but leaves the caller to guess field names and id conventions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for both parameters and provides nothing. It doesn't state whether video_id accepts a bare 11-character id or a full URL, and never explains that api_key is a caller-supplied YouTube Data API credential rather than an internal identifier.

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?

Clear verb+resource: retrieves metadata, statistics and content details for a single YouTube video. This distinguishes a detail lookup from list/search-shaped siblings like youtube_search, but the description never names those siblings explicitly, so the differentiation is left implicit.

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?

No when-to-use guidance at all. It doesn't say to call this after youtube_search resolves a video id, nor does it distinguish it from youtube_get_captions or youtube_get_channel, leaving the agent to infer the workflow from the tool name alone.

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