Skip to main content
Glama

youtube_my_account

Read-only

Retrieves the authenticated YouTube channel tied to the connected account, confirming which channel an AI assistant is authorized to manage.

Instructions

Get the authenticated YouTube channel.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description needs to add context and does not. It says nothing about what happens when the caller is not authenticated (error vs empty result) or what channel fields are returned, both of which are the real unknowns for a zero-argument getter.

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?

A single seven-word sentence with no filler or repetition. The identifying qualifier ('authenticated') is front-loaded where it matters most.

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?

With no parameters and no output schema, the main remaining unknown is what the returned channel object contains and how auth failure surfaces, and the description covers neither. It is adequate for selection but leaves the agent guessing about the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters at all, so there is nothing for the description to disambiguate; the baseline of 4 applies. The sentence correctly implies the channel identity is derived from the caller's credentials rather than an argument.

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 and resource ('Get the authenticated YouTube channel'), and the qualifier 'authenticated' signals it returns the caller's own channel rather than an arbitrary one. It does not explicitly name how it differs from the closely related siblings youtube_get_channel or youtube_auth_status, so an agent must infer the split.

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?

Usage is only implied: 'authenticated' suggests using this for the caller's own channel versus youtube_get_channel for a specified one, but the description never states when to use it, when not to, or which sibling to pick. No prerequisites or preconditions are mentioned.

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