Multilingual YouTube → Knowledge Pack engine. Paste a video URL and get a structured pack — summary, key ideas, glossary, quiz, transcript with timestamps — in Spanish, Portuguese, German, or English. Anonymous endpoint plus OAuth-gated tools for library search, RAG Q&A on a single pack, and Anki export.
Use this when the user asks for a summary, key ideas, or study material from a YouTube video. Returns a structured Knowledge Pack: title, short summary, key ideas, and a link to the full pack on vozclara.app. Pass format="obsidian" to get vault-ready Markdown with YAML frontmatter the user can save to their second brain.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public YouTube video URL (youtube.com/watch?v=… or youtu.be/… short form). | |
| depth | No | Depth of the generated pack. `short` = one-paragraph summary. `standard` = summary + 3-5 key ideas. `deep` = summary + key ideas + glossary + quiz. | standard |
| format | No | Output format. `standard` = plain prose for chat. `obsidian` = Markdown with YAML frontmatter (source, videoId, languages, tags) ready to write straight into an Obsidian vault or any Markdown knowledge base. Use `obsidian` when the user asks to save the pack to their vault / second brain / notes. | standard |
| language | Yes | Output language for the Knowledge Pack: es (Spanish), pt (Portuguese), de (German), en (English). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility. It discloses the tool returns a structured pack with specific components and a link. It does not mention rate limits, processing time, or authentication needs, but for a read-only generation tool, the transparency is adequate. A slight gap is the lack of statement about non-destructiveness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, with the first sentence front-loading the purpose and trigger, and the second detailing the return value and format guidance. Every sentence serves a clear purpose with zero redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of output schema and annotations, the description adequately covers purpose, when to use, key parameter behavior, and return structure. It could include a note about the full link being accessible on vozclara.app, but overall it is sufficiently complete for an agent to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds value by explaining when to use `obsidian` format and the effect of different `depth` values (e.g., `short` = one-paragraph summary). This provides context beyond the schema's simple enum descriptions, warranting a 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool generates a Knowledge Pack from a YouTube video, listing the returned fields (title, summary, key ideas, link). It unambiguously defines the verb and resource, and implicitly distinguishes from any potential sibling by focusing on YouTube videos.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells when to use: 'when the user asks for a summary, key ideas, or study material from a YouTube video.' It also provides specific advice for the `format` parameter, guiding agents to use `obsidian` for vault-saving requests. No sibling tools exist, so exclusion guidance is unnecessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
vozclara_generate_pack1 field changedInput schema / properties / formatAdded value: +{
+ "default": "standard",
+ "description": "Output format. `standard` = plain prose for chat. `obsidian` = Markdown with YAML frontmatter (source, videoId, languages, tags) ready to write straight into an Obsidian vault or any Markdown knowledge base. Use `obsidian` when the user asks to save the pack to their vault / second brain / notes.",
+ "enum": [
+ "standard",
+ "obsidian"
+ ],
+ "type": "string"
+}vozclara_generate_packClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Add one secure layer between your agents and this server.
With only one tool, there is no possibility of confusion between tools. The single tool has a clearly defined purpose.
The single tool name 'vozclara_generate_pack' follows a consistent verb_noun pattern (generate_pack), which is clear and standard.
A single tool for generating knowledge packs is borderline appropriate. While it may cover the core functionality, the server feels thin and could benefit from additional tools for managing packs or supporting different workflows.
The toolset is severely incomplete for a service that generates and presumably manages knowledge packs. Missing CRUD operations (e.g., listing, updating, deleting packs) and other potential features like retrieving transcripts or supporting multiple formats beyond Obsidian.