tubemind-secure-mcp

get_channel_analytics

Retrieve daily YouTube channel analytics for a date range: views, likes, comments, subscribers gained, watch time, and average view duration, grouped by day.

Instructions

Retorna métricas reais do canal autenticado via YouTube Analytics API: views, likes, comentários, inscritos ganhos, minutos assistidos e duração média. Agrupa por dia no período informado.

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": "get_channel_analytics"
  }
}

Input Schema

Name	Required	Description
`endDate`	Yes	Data final no formato YYYY-MM-DD
`metrics`	No	Métricas desejadas (1–6). Default: views, likes, subscribersGained
`startDate`	Yes	Data inicial no formato YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Aug 11, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description must carry the burden of behavioral disclosure. It mentions 'authenticated channel' and 'returns', implying a read-only operation, but does not disclose potential rate limits, error handling, pagination, or side effects. This leaves significant behavioral ambiguity.

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?

The description is two short sentences, front-loaded with the core purpose and a clear list of metrics. Every word contributes value, with no redundancy or irrelevant detail.

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?

Without an output schema, the description does not fully specify the return structure. It lists the metrics and mentions daily grouping, but omits details such as the exact response format, timezone handling, or authentication steps, leaving room for inference.

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%, so the baseline is 3. The description lists the available metrics which are already in the schema's enum, and adds the context of daily aggregation, but does not provide additional syntactic or default information beyond what the schema already offers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as returning real channel analytics metrics via the YouTube Analytics API, listing specific metrics and stating daily grouping. This distinguishes it from sibling tools that focus on keywords, video metadata, or competitive analysis.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, exclusions, or comparisons with sibling tools such as list_channel_videos or benchmark_channel, leaving the agent to infer usage from the name and description alone.

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

Deploy Server