Skip to main content
Glama

Google Videos Retrieve Content

google-videos-retrieve-content
Read-only

Retrieve generated video content from a finished Google video operation. Returns resource links or base64 blobs.

Instructions

Download generated video content for a completed Google video operation, write it under MEDIA_GEN_DIRS, and return content blocks (tool_result=resource_link|resource).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operation_nameYesGoogle video operation name/id.
indexNoWhich generatedVideos[index] to download (default: 0).
tool_resultNoControls content[] shape: 'resource_link' (default) emits ResourceLink items, 'resource' emits EmbeddedResource blocks with base64 blob.resource_link
response_formatNoControls structuredContent video fields: 'url' (default) prefers video.uri, 'b64_json' prefers video.videoBytes.url
Behavior4/5

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

Discloses the side effect of writing to MEDIA_GEN_DIRS, which goes beyond the readOnlyHint and destructiveHint annotations. The description adds useful behavioral context not captured in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is adequate but packs multiple actions (download, write, return) into one clause, reducing clarity. Could be more straightforward.

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

Completeness3/5

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

Lacks output schema and does not describe the exact return value format beyond referencing content blocks. Given the complexity, a short description of the returned structure would be beneficial.

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 100% description coverage, already explaining all parameters. The description mentions tool_result=resource_link|resource, but this adds no new meaning beyond what the schema provides.

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?

Clearly states it downloads generated video content for completed Google video operations, distinguishing it from generation and retrieval of operation status. However, it does not explicitly differentiate from similar sibling tools like openai-videos-retrieve-content.

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

Usage Guidelines3/5

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

Implies usage after a completed generation operation but provides no explicit guidance on when to use this tool versus alternatives or when not to use it.

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/strato-space/media-gen-mcp'

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