Skip to main content
Glama

Is YouTube connected

youtube_status

Verify YouTube publishing readiness for Clips Kitty: see if uploads are allowed now, which channel is connected, and today's remaining upload quota before planning a batch.

Instructions

Whether Clips Kitty can publish to YouTube right now, which channel, and how many uploads are left today. Check this before planning a batch.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations available, the description carries the full burden and does disclose the meaningful behavioral traits: current connect state, the target channel, and a per-day upload quota that constrains batching. It stops short of describing the response shape or what an unconnected state looks like, which matters since there is no output schema.

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?

Two sentences, zero filler: the substantive status claim leads and the actionable instruction follows. Nothing repeats the title or name unnecessarily.

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 status check with no annotations and no output schema, the description covers the essentials an agent needs to decide to call it and to interpret the answer. The only remaining gap is the exact return shape, which has no structured field to carry it.

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, so the baseline of 4 applies; there is nothing for the description to disambiguate at the input level.

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 and scope: YouTube publish readiness for Clips Kitty, the connected channel, and remaining daily uploads. The platform naming implicitly separates it from uploadpost_status and woopsocial_status, but it never explicitly contrasts itself with those siblings, so differentiation relies on inference.

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

Usage Guidelines4/5

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

"Check this before planning a batch" gives a concrete when-to-use signal tied to a pre-flight workflow. It offers no exclusions or named alternatives (e.g. when publish_status would be the better call), which keeps it just short of the top band.

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