Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

transcript_youtube_info

Retrieve top-level YouTube video metadata—title, author, duration, and caption tracks—as YAML for quick reference.

Instructions

Fetch top-level metadata about a YouTube video (title, author, duration, available caption tracks) as YAML. Read-only. Mirrors omni-dev transcript youtube info.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "transcript_youtube_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video URL or bare 11-character video ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `transcript_youtube_info` and\n`transcript_youtube_list_langs` tools."
    • removedInput schema / title
      Removed value: -"TranscriptLocatorParams"
  2. Addedv0.32.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. States 'Read-only' and output as YAML, but lacks details on error handling, rate limits, or auth requirements.

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, front-loaded with purpose, read-only status, and CLI reference. No fluff.

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 simple metadata fetch with one parameter and no output schema, description covers purpose, output format, and read-only nature. Adequate but could mention behavior on invalid URLs.

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 has one param 'url' with full coverage. Description adds no extra semantics beyond what the schema already provides.

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?

Description clearly states it fetches top-level metadata (title, author, duration, caption tracks) as YAML, distinguishing it from sibling tools that fetch transcript or list languages.

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?

Specifies 'Read-only' and mirrors a CLI command, implying use for metadata retrieval. No explicit when-not, but context from siblings provides differentiation.

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