Skip to main content
Glama

draft_description

Read-only

Draft a YouTube video DESCRIPTION for the signed-in user, in their own voice and structure (learned from the descriptions they already write). Call this when the user asks to write, draft, rewrite, or improve a video description, or the text/notes/blurb under a video. Pass video to improve an existing upload's description, or idea for a new video, plus title when a title has already been agreed. This is for the description text only; for titles and thumbnails use package_video.

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

Input Schema

NameRequiredDescriptionDefault
ideaNoWhat a new video is about
titleNoThe title already agreed for a new video, if there is one
topicNo
videoNoAn existing upload of theirs whose description to improve (name the upload)
video_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: the draft is personalized to the user's own established voice and structure, learned from their existing descriptions. It does not say whether the draft is persisted anywhere or returned only as text, which is the remaining gap.

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?

Front-loaded with the action and deliverable, then trigger conditions, then parameter routing, then the sibling exclusion. Every sentence carries distinct information and none restates the tool name.

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?

There is no output schema, so the description should ideally indicate what comes back (a text draft only, not a published change) and whether anything is written. It compensates well on inputs and routing, but the two undocumented duplicate-looking parameters keep it short of complete.

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?

With 60% schema coverage, the description usefully adds meaning to `video` (an existing upload whose description to improve), `idea` (for a new video), and `title` (already agreed). However, `topic` and `video_title` are undocumented in both the schema and the description, leaving an unresolved overlap with `idea` and `title` that an agent cannot disambiguate.

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?

Specific verb plus resource: "Draft a YouTube video DESCRIPTION for the signed-in user." It also qualifies the output as being in the user's own voice and structure, and explicitly distinguishes itself from package_video, so an agent can route without opening the schema.

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

Usage Guidelines5/5

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

Names the triggering user intents (write, draft, rewrite, improve, the text/notes/blurb under a video) and the routing rule between `video` for an existing upload versus `idea` for a new one, plus `title` when a title has already been agreed. It also names the exclusion: titles and thumbnails belong to package_video.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources