Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_consumption_trends

Read-only

Compare YouTube consumption topics across two date ranges to identify shifts in viewing interest. Enter baseline and comparison dates to see which topics gained or lost attention.

Instructions

Compare local consumption topics across two date ranges.

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": {
      "baselineStartDate": "<baselineStartDate>",
      "baselineEndDate": "<baselineEndDate>",
      "comparisonStartDate": "<comparisonStartDate>",
      "comparisonEndDate": "<comparisonEndDate>"
    },
    "name": "youtube_consumption_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
baselineEndDateYesEnd date of the baseline period, YYYY-MM-DD.
baselineStartDateYesStart date of the baseline period, YYYY-MM-DD.
comparisonEndDateYesEnd date of the comparison period, YYYY-MM-DD.
comparisonStartDateYesStart date of the comparison period, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.1
    • addedInput schema / properties / baselineEndDate / description
      Added value: +"End date of the baseline period, YYYY-MM-DD."
    • addedInput schema / properties / baselineStartDate / description
      Added value: +"Start date of the baseline period, YYYY-MM-DD."
    • addedInput schema / properties / comparisonEndDate / description
      Added value: +"End date of the comparison period, YYYY-MM-DD."
    • addedInput schema / properties / comparisonStartDate / description
      Added value: +"Start date of the comparison period, YYYY-MM-DD."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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, and the description adds only the word 'local', implying it operates on stored watch data rather than the live API. It says nothing about what the comparison returns, whether periods must be equal length, or how results are ranked.

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 front-loaded sentence with no filler. It is efficient, though the terseness leaves key behavioral questions unanswered rather than being genuinely optimal.

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?

With no output schema, an agent cannot know what the comparison produces (topic deltas? rankings? percentages?). The description also does not explain the concept of 'consumption topics' or constraints on the two ranges, leaving the tool under-specified for its analysis role.

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 description coverage is 100%, so all four date parameters are fully documented with format and role. The description only implicitly confirms the baseline/comparison pairing already encoded in the parameter names, adding little beyond the schema.

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 (compare) with a resource (local consumption topics) and a scope (across two date ranges). It is clear enough to distinguish from youtube_consumption_profile, though it never names that sibling or clarifies what a 'topic' is.

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 guidance, no mention of prerequisites (e.g., needing local watch history), and no reference to the closely related youtube_consumption_profile or youtube_trending tools. The agent must infer all routing decisions.

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