Skip to main content
Glama

omniseek_view

View embedded images, document figures, and video frames directly from URLs, files, or video links. Auto-detects source type and returns visual content for immediate inspection.

Instructions

SEE with your own vision, IN-BAND — document figures, loose image URLs, or video frames. ONE verb; kind="auto" picks the branch (or force it with kind=document|images|video).

Fully-qualified MCP name: mcp__omniseek__omniseek_view (server name is omniseek; there is no omniseek-eye server).

ROUTING (kind="auto"): a document path/extension (.pdf/.pptx/.docx/.xlsx/…, as in omniseek_read) → DOCUMENT figures; a video URL (youtube/bilibili/douyin host or a .mp4/.webm/.mov suffix) → VIDEO frames; otherwise → loose IMAGE URLs (target may be a comma-separated URL list). The images come back as image content you can look at directly (no download/scp dance); OmniSeek only renders the pixels, what they MEAN is yours to read.

WHICH PARAMS BELONG TO WHICH KIND: • document: sections (comma-separated slide/page numbers to pull, "" = all), names (comma-separated exact image names from the omniseek_read outline media[].name), max_images (full-res cap; a wider selection falls back to a contact sheet). THE TWO-STEP: first omniseek_read to get the outline (which slides/pages hold images), then call this — with NO sections/names you get a CONTACT SHEET (every image a labeled thumbnail tiled into one montage; triage ~30 for the cost of one), then pull the few that matter full-res by sections="8,15" or names="s08_02_image.png". Covers pptx / pdf / docx (the image-bearing formats); text formats return a note. render_pages="8,15" is the COMPLEMENT (PDF): it renders those WHOLE pages to images, the channel for a page whose substance is VECTOR figures / dense tables / a layout carrying NO embedded raster (where sections/names find nothing). This is how you READ a visual page you cannot trust as parsed text: route to the doc, omniseek_read for the page you want, then render + see it with your own vision. • images: target = image URLs comma/space/newline separated (paste a walled post's media[] list — xiaohongshu / zhihu note images, where the 干货 often lives). max_images caps per call. • video: start / duration (optional slice: "8:30", "90", "1:02:30"; default the whole video, capped at 30 min), n (frames to sample, default 12, max 24). The VISUAL half of omniseek_transcribe: its on-screen slides / diagrams / code / charts as ONE labeled contact sheet (a timestamp under each frame). Pair with omniseek_transcribe on the same slice for BOTH halves. (bilibili frames ride the same activated playurl session as bilibili audio — the ASR path's visual sibling.)

Returns image content blocks: document = [contact-sheet montage + legend] or [manifest + one block per figure]; images = [manifest + one block per URL that loaded]; video = [contact-sheet + timestamp legend]. Or an error / honest "nothing to show" note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
kindNoauto
namesNo
startNo
targetYes
durationNo
sectionsNo
max_imagesNo
render_pagesNo
contact_sheetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It explains it returns image content blocks, can produce contact sheets or manifests, falls back to honest 'nothing to show' notes, applies caps, and avoids any download/scp step. It even notes the bilibili session dependency for video frames.

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 description is long, but the length is justified by the tool's polymorphic behavior and 10 parameters. It is well-organized with clear headings and per-kind parameter groupings, though some rhetorical flourishes and redundant emphasis could be trimmed without losing information.

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?

Given the complex branching behavior, 10 parameters, and no output schema, the description is remarkably complete. It covers routing, per-kind parameters, return formats, limits, fallback behavior, the required omniseek_read prerequisite, and relationships to sibling tools.

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 description coverage is 0%, and the description compensates strongly by explaining target, kind, sections, names, max_images, render_pages, start, duration, and n with concrete formats and defaults. However, the contact_sheet boolean is only implied through repeated contact-sheet behavior, not explicitly tied to the parameter.

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 a specific verb and resource: 'SEE with your own vision' across document figures, image URLs, and video frames. It also distinguishes itself from siblings like omniseek_read and omniseek_transcribe by positioning itself as the visual counterpart and the two-step outline workflow.

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?

Routing rules are explicit: kind='auto' sends document paths/extensions to document figures, video URLs/suffixes to video frames, and everything else to image URLs. It also gives clear when-to-use guidance for render_pages on vector-heavy pages, and recommends pairing with omniseek_transcribe for both visual and audio halves.

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