Skip to main content
Glama

youtube_creator_top_videos

Read-only

Retrieve top owned-channel YouTube videos for a specified date range and optional limit to identify high-performing content.

Instructions

Get top owned-channel videos 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_top_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of top videos to return, 1-50; omit to use the tool default.
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. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / endDate / description
      Added value: +"End date of the range, YYYY-MM-DD."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of top videos to return, 1-50; omit to use the tool default."
    • addedInput schema / properties / startDate / description
      Added value: +"Start date of the range, YYYY-MM-DD."
  2. First observedv0.1.0

TDQS

C2.6/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, so the description should supply what annotations cannot: the ranking metric behind 'top', whether ties are broken, or default limit behavior. It supplies none of that, restating only the date-range scoping the schema already enforces via required startDate/endDate.

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 zero filler and no redundancy. It is efficient, though the brevity is partly under-specification rather than discipline.

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?

No output schema exists, so the description should at least explain what 'top' returns and how ordering works; it does neither. For an analytics-style ranking tool the agent cannot predict the result set shape or ranking basis from the definition.

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 both date parameters and the limit bound (1-50) are fully documented in the schema. The description's phrase 'for a date range' merely echoes required params and adds no format or semantics beyond the schema, 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 sentence names a verb ('Get'), a resource ('top owned-channel videos'), and a scope ('date range'), so the basic purpose is legible. But 'top' is never defined (ranked by views, watch time, engagement?), which is the single most decision-relevant fact about this tool, and it doesn't distinguish itself from nearby siblings like youtube_list_owned_videos, youtube_creator_overview, or youtube_creator_retention.

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 indication of when to use this instead of youtube_list_owned_videos or youtube_creator_overview, and no prerequisites or exclusions. The agent must infer applicability purely from the name.

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