ytmcp

get_analytics

Retrieve YouTube channel analytics—views, watch time, and subscriber gains or losses—for a specified reporting period in days.

Instructions

Get channel analytics (views, watch-time, subscribers gained/lost).

Args: channel_id: Channel id. period_days: Reporting window in days (default 28).

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_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`channel_id`	Yes
`period_days`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It conveys the read-only 'Get' nature and names the metric categories, but says nothing about auth requirements, data freshness/lag, or rate limits. It avoids misleading claims, but leaves real behavioral gaps for a tool with zero annotation coverage.

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?

Compact and front-loaded: purpose first, then an Args block with no filler sentences. The Args block largely restates schema field titles, so it is efficient but not maximally information-dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 format need not be described. For a simple two-parameter read tool, the description covers purpose and both parameters adequately; only usage routing against siblings and basic access/freshness context are absent.

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 0%, so the description must compensate, and it does minimally: it glosses channel_id and explains period_days as a 'Reporting window in days' with default 28. That adds slight semantic value over the bare schema titles, but offers no format, accepted range, or unit conventions beyond the default.

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+resource ('Get channel analytics') and enumerates the returned metrics (views, watch-time, subscribers gained/lost), which is more specific than most siblings. However, it never explicitly distinguishes itself from adjacent tools like get_channel_info or get_subscriber_count, leaving some overlap for the agent to resolve.

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?

The description says nothing about when to use this tool versus the ~20 siblings, nor any prerequisite such as channel ownership, permissions, or whether analytics require a minimum account age. The agent must infer usage entirely from the name.

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