Skip to main content
Glama

Zoom

media_zoom
Read-only

Extracts a single readable frame from a local video at a given timestamp or window, or renders one page of a local document, optionally cropped, so you can read on-screen text or details that storyboard grids are too small to show.

Instructions

Get a close-up of one moment in a local video, or one page of a local document, returned as a single image. (取本地视频某一时刻的特写单帧,或本地文档某一页的整页 / 局部放大图。)

Use it after media_overview when one cell or page needs a closer look: "what exactly is on screen at 01:12?" "what does line 3 of page 7 say?"

For video, pass at (a single timestamp) or start/end (a window — the sharpest frame inside it is returned, and the exact timestamp is reported back). For a document, pass page, optionally with crop. crop is {x, y, width, height}, each a fraction 0..1 of the frame or page, origin top-left.

Keep it to one frame. It costs roughly 1,900 vision tokens — far more than a whole overview cell. Zoom the parts that matter instead of re-scanning the file.

This is the ONLY tool whose image is meant for reading. A storyboard cell is a few hundred pixels wide and the text inside it is unreadable; a cropped single frame at up to 1600 px is readable. So: locate in the overview grid, then zoom to read. The returned image is always source "visual" — what you read off it is your own reading of pixels, not a transcript, so treat it as an observation rather than a quotation.

Input Schema

NameRequiredDescriptionDefault
atNoExact timestamp in seconds for a video frame. Mutually exclusive with start/end. Applicable to video only. (精确时刻,秒)
endNoWindow end in seconds (closed interval, both ends included). Applicable to video and audio only. Defaults to the end of the media; a value past the end is clipped and reported. (终点,秒)
cropNoCrop rectangle {x, y, width, height}: all four required, each a fraction 0..1 of the frame or page, origin top-left. Applicable to video and document only. (裁切区域,比例制)
pageNo1-based page number to render. Required for document media; not applicable to video. (页码)
pathYesAbsolute path to a LOCAL file: video, audio recording, or document. URLs and relative paths are rejected — this server never downloads anything. (本地文件绝对路径)
startNoWindow start in seconds (closed interval, both ends included). Applicable to video and audio only; document media uses "pages" instead. Default 0. (起点,秒)
maxEdgeNoLongest edge of each image in pixels: 256-1600. Default 1280 for overview, 1600 for zoom. Applicable to video and document only. (单张图最长边)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly and closed-world annotations, the description discloses cost (~1,900 vision tokens), output nature (single image, source 'visual'), and an important interpretive limitation: reading pixels is an observation, not a transcript or quotation. It also explains that for video windows the sharpest frame is returned and the exact timestamp is reported back.

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

Conciseness4/5

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

The English portion is front-loaded, clearly structured, and every sentence carries useful guidance about purpose, routing, cost, and interpretive caveats. The main inefficiency is the full bilingual duplication, which roughly doubles the description size without adding new semantic content for an agent.

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 7-parameter tool with no output schema, the description is nearly complete: it explains the returned image, its visual source, the video/document modes, and the read-after-overview workflow. One gap is that the schema accepts audio paths and start/end for audio, while the description only frames the tool around video and documents.

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 coverage is 100%, so the baseline is 3. The description still adds meaningful semantics beyond the schema: at versus start/end behavior, the sharpest-frame-inside-window rule, exact timestamp reporting, and crop as fractional coordinates with top-left origin.

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 states a specific verb and resource: get a close-up of one moment in a local video or one page of a local document, returned as a single image. It explicitly distinguishes itself from media_overview by saying the image is meant for reading, not just navigation, and by noting storyboard cells are too small to read.

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?

It routes the agent explicitly: use this after media_overview when one cell or page needs a closer look, with concrete questions like 'what exactly is on screen at 01:12?' and 'what does line 3 of page 7 say?'. It also warns to keep it to one frame and zoom only the parts that matter rather than re-scanning the whole file.

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