Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_creator_retention

Read-only

Retrieve audience-retention data for an owned YouTube video to identify drop-off points and improve content performance.

Instructions

Get audience-retention data for an owned 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": {
      "videoId": "<videoId>"
    },
    "name": "youtube_creator_retention"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesID of an owned video to report audience retention for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / videoId / description
      Added value: +"ID of an owned video to report audience retention for."
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the access constraint that the video must be owned, which is useful, but says nothing about what the retention data contains (curve points, time windows, averages) or any limits. With annotations carrying the safety profile, this is adequate but thin.

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 clean sentence with the resource and scope front-loaded and zero filler. It is efficient, though so terse that it borders on under-specification rather than optimal density.

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?

A single-parameter read tool with an annotation is low-complexity, and no output schema exists, so the description should hint at what retention data is returned. It does not, leaving the agent unable to predict the response shape or any time-range behavior.

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% and the sole parameter's schema text ('ID of an owned video to report audience retention for') already carries the meaning. The description restates the same 'owned video' constraint without adding format, sourcing, or validation detail, so baseline 3 applies.

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?

The description names a specific verb ('Get') and resource ('audience-retention data') scoped to an 'owned video', which separates it from siblings like youtube_creator_overview or youtube_get_video. It does not explicitly contrast with the closest analytics siblings (youtube_creator_report, youtube_creator_top_videos), so it stops short of a 5.

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 guidance on when to choose this tool over youtube_creator_report, youtube_creator_overview, or youtube_creator_top_videos. The only implicit constraint is that the video must be owned, which comes from the word 'owned' rather than an explicit when-to-use statement.

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