yt-consolidado

get_first_published_date

Return the oldest publication date of a YouTube channel to establish its age and first upload. Use it to verify channel history or filter channels by how long they have been active.

Instructions

Oldest publication date of a channel. Did not exist in any original.

Layer: Data API. Quota: 1 unit (channel creation proxy), plus 1 unit per 50
uploads when enumeration runs — when the channel is younger than
``enumerate_if_younger_than_days`` or has at most
``enumerate_if_video_count_under`` uploads (0 = never enumerate on size).

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": {
      "channel_id": "<channel_id>"
    },
    "name": "get_first_published_date"
  }
}

Input Schema

Name	Required	Description	Default
`max_pages`	No
`channel_id`	Yes
`enumerate_if_video_count_under`	No
`enumerate_if_younger_than_days`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does valuable work by disclosing the quota cost model (1 unit plus 1 per 50 uploads) and the conditions that trigger enumeration, but it never says whether enumeration is an implicit side effect, what is returned when enumeration is skipped, or what permissions are needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The quota sentence is front-loaded and informative, but the bold 'Did not exist in any original' fragment is unexplained filler, and the enumeration condition wraps awkwardly mid-sentence with backticked placeholders.

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?

An output schema exists, so return values need not be described, and the quota/enumeration behavior is covered. However, half the parameters and all caller-facing usage context are missing, which is a notable gap for a tool with a non-obvious cost and conditional side effect.

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 must explain all four parameters. It clarifies only two: enumerate_if_younger_than_days and enumerate_if_video_count_under (including '0 = never enumerate on size'). max_pages and the required channel_id are left entirely unexplained.

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 first sentence names the resource and the returned value ('Oldest publication date of a channel'), but it largely restates the tool name and never uses a clear verb. The tagline '**Did not exist in any original.**' is cryptic and adds no distinguishing information versus siblings such as get_channel_details or get_channel_rss_videos.

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 statement of when to use this tool, when not to, or which sibling to prefer for channel-date questions. The only conditional language describes internal enumeration triggers, not caller-facing usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server