Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_channel_lives

Retrieve live and past YouTube channel streams by channel ID or handle, and use continuation tokens to page through results.

Instructions

youtube: Channel Lives. GET /v1/youtube/channel/lives. Provide one of: channelId, handle, continuationToken. Get live streams and past streams from a YouTube channel. Can pass channelId or handle. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_channel_lives"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoYouTube channel handle
channelIdNoYouTube channel ID
continuationTokenNoUse continuationToken from the previous response to get the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does real work: it discloses the HTTP method (implying a read), the credit cost on success, and an explicit no-charge policy for errors, blocked, timed-out, invalid requests and cache hits. The main gap is that it says nothing about response shape, ordering, or pagination semantics beyond the existence of continuationToken.

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?

Purpose is front-loaded, followed by the route, the parameter rule, and the cost policy, so an agent can stop reading early. The cost sentences are somewhat verbose and the clause 'Can pass channelId or handle' partially repeats the preceding 'Provide one of' line.

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?

For a 3-parameter, no-annotations, no-output-schema tool, the definition covers invocation and billing but not results: an agent cannot tell how live versus past streams are marked, whether continuationToken is the only pagination mechanism, or what an empty payload means. It is adequate but leaves meaningful gaps relative to the complexity.

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; each parameter already carries its own description and examples. The description does add one thing the schema does not express — that exactly one of channelId/handle/continuationToken should be supplied (schema shows zero required properties and no oneOf) — which merits keeping it at the baseline rather than going lower.

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?

The description names a specific verb and resource: get live streams and past streams from a YouTube channel, plus the underlying route GET /v1/youtube/channel/lives. That is enough to separate it from youtube_channel_videos and youtube_channel_shorts, though it never explicitly contrasts with them, and 'live streams and past streams' is slightly ambiguous about whether completed broadcasts are included.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a selection rule for the identifier parameters ('Provide one of: channelId, handle, continuationToken') and explains when a call is free versus charged, which is useful invocation context. But it offers no guidance on when to choose this tool over sibling channel endpoints, and no exclusions or prerequisites such as channel visibility or auth.

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