Skip to main content
Glama
AVS845

screenshot-vision-mcp

by AVS845

analyze_screenshot

Capture a screenshot of any public URL and analyze it with a local vision model to answer questions about the page. Supports full-page captures for detailed inspection.

Instructions

Take a screenshot of a URL in a headless browser and analyze it with a local Ollama vision model. Good for public pages. For pages requiring login, use capture_window instead. Use full_page: true to capture content below the fold — the page is sliced into segments and sent as multiple images so no detail is lost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to screenshot (e.g. http://localhost:3004)
modelNoOllama vision model to use (defaults to OLLAMA_MODEL env var, or gemma4:e4b)gemma4:e4b
wait_msNoMilliseconds to wait after page load for JS rendering
questionYesWhat to analyze or look for in the screenshot
full_pageNoCapture the full page height, not just the visible viewport. Long pages are sliced into segments sent as multiple images so detail is preserved at every scroll depth.
max_slicesNoMaximum number of slices when full_page is true. Slices are distributed evenly across the page height. Default 8 covers most pages well.
viewport_widthNoViewport width in pixels
viewport_heightNoViewport height in pixels
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the tool runs a headless browser, uses a local Ollama vision model, and explains the slicing mechanism for full-page captures to preserve detail. This goes beyond the schema and provides meaningful insight into how the tool behaves, though it omits return format and potential side effects.

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?

The description is two sentences, front-loaded with the primary purpose, followed by usage guidance and a key behavioral note. Every sentence earns its place with no redundancy or filler.

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?

The description covers the main use case, login-page alternative, and full-page behavior, but it does not explicitly specify what the tool returns (e.g., analysis text, screenshot, or both). Given the absence of an output schema, this is a notable gap for a tool with 8 parameters and a potentially complex response.

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 description coverage is 100%, so the baseline is 3. The description reinforces the full_page parameter's behavior ('sliced into segments and sent as multiple images') but does not materially add meaning beyond what the schema already documents for other parameters.

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 action ('Take a screenshot of a URL in a headless browser and analyze it with a local Ollama vision model') and distinguishes the tool from siblings by explicitly contrasting with capture_window for login pages. This makes the tool's purpose unambiguous and clearly differentiated.

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?

The description gives explicit usage context: 'Good for public pages' and directs users to 'use capture_window instead' for login-protected pages. It also advises on full_page usage for content below the fold, covering when to use this tool versus an alternative.

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/AVS845/screenshot-vision-mcp'

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