Skip to main content
Glama
MKirovBG

scribefy-mcp

Search YouTube videos by free-text query

search_videos

Search YouTube for videos matching a query, returning title, channel, duration, view count, and URL.

Instructions

Search YouTube for videos matching a query string. Returns up to limit results (default 10, max 25) with title, channel, duration, view count, and URL. Free — no credits charged. Use this when the user asks 'find me videos about X' before chaining into extract_transcript on a specific result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFree-text search query. Same syntax YouTube's own search bar accepts.
limitNoMax results to return (1–25, default 10).
Behavior4/5

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

No annotations provided, but description discloses default limit, max, and that it's free. Does not mention sorting or pagination, but the return fields are fully listed.

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, first states purpose and key behavior, second gives usage guidance. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with two well-documented parameters and no output schema, the description covers purpose, behavior, constraints, cost, and chaining instructions completely.

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?

Schema covers both parameters with descriptions; description adds valuable context on query syntax (same as YouTube search bar) and default/max for limit.

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?

The description clearly states the tool searches YouTube videos by query and lists returned fields. It distinguishes from sibling 'extract_transcript' by mentioning chaining.

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?

Explicitly advises using this tool when user asks to find videos, and to chain with 'extract_transcript' on a result. Also notes it's free and no credits charged.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MKirovBG/scribefy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server