Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_creator_overview

Read-only

Retrieve owned-channel creator analytics for a specified date range to review performance and track channel trends.

Instructions

Get owned-channel creator analytics for a date range.

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "youtube_creator_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYesEnd date of the range, YYYY-MM-DD.
startDateYesStart date of the range, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / endDate / description
      Added value: +"End date of the range, YYYY-MM-DD."
    • addedInput schema / properties / startDate / description
      Added value: +"Start date of the range, YYYY-MM-DD."
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the meaningful constraint that this only works on the caller's own channel ('owned-channel') and that results are bounded by a date range, but it says nothing about aggregation granularity, metric set, or whether data lags.

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?

A single front-loaded sentence with zero filler; the scope qualifier comes last where it belongs. Nothing is repeated or wasted.

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 low-complexity read-only tool with two fully documented parameters and no output schema, the description is nearly sufficient. The gap is that 'analytics' is undefined — with four sibling creator-analytics tools, an agent needs at least a hint of what this overview returns to choose it correctly.

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 both date parameters fully documented including the YYYY-MM-DD pattern, so the schema does the heavy lifting. The description only restates 'date range' and adds no semantics such as timezone, inclusive bounds, or maximum span.

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?

States a specific verb ('Get'), resource ('owned-channel creator analytics'), and scope ('for a date range'), which is far better than a tautology. However, it never distinguishes itself from the several creator-analytics siblings (youtube_creator_report, youtube_creator_retention, youtube_creator_top_videos), so an agent cannot tell from the text which analytics surface this returns.

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, when-not-to-use, or alternative-routing guidance. The description does not say whether this is a summary dashboard call versus a detailed report, nor does it point to youtube_creator_report or youtube_creator_retention as the alternative for narrower questions.

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