Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Show which credentials are available

auth_status
Read-onlyIdempotent

Check which YouTube credentials are available—API key, OAuth token, both, or neither—and which tools work with them. Get next steps for enabling unsupported capabilities without opening a browser.

Instructions

Which credentials are available (API key, OAuth token, both, or neither) and which tools work with them.

Includes next steps for enabling anything unsupported. Never opens a browser.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context the annotations do not provide: it will never open a browser, so the agent should not expect an interactive OAuth flow, and the response includes actionable next steps for unsupported capabilities. It stops short of saying whether the check performs a network round-trip or can fail.

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?

Three short sentences with zero filler, front-loading the core answer (which credentials exist) before the secondary detail (next steps) and the caveat (no browser). Every sentence adds information.

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?

For a zero-parameter, read-only status tool with a full output schema and safety annotations, the description covers what an agent needs: what it reports, what else it returns, and that it will not trigger an interactive flow. It could go slightly further by noting that results reflect the current process/configuration state.

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?

The tool takes zero parameters, which normally sets a baseline of 4, but there is nothing parameter-wise for the description to clarify. Its enumeration of credential states is closer to return-value documentation, which the existing output schema already carries, so it earns baseline rather than bonus credit here.

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 resource — credential availability — and enumerates the exact outcomes it reports (API key, OAuth token, both, or neither), plus the secondary result of which tools work. That is far more concrete than the bare tool name and clearly separates it from the analytics siblings. The only weakness is that the action is expressed as a noun phrase rather than a verb, but the intent is unambiguous.

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?

There is no explicit when-to-use statement, no prerequisite, and no named alternative. Usage is only implied: an agent can infer it should call this to learn which other tools are usable with the current credentials. That inference is reasonable but the description never says so directly.

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