Skip to main content
Glama
Gwakko

agent-in-browser

by Gwakko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

screenshot

Read-only

Capture a tab's visible viewport as a PNG to inspect visual layout, colors, or images, and optionally save it to a file path for later review.

Instructions

Read-only: capture the visible viewport of a tab as a PNG image returned to you (full-page capture is not supported: scroll and capture again). Use it to check visual layout, colours or images, since snapshot and get_text only describe structure and text. Pass path to also save the file, creating folders as needed; the result then includes the saved path. Size follows the viewport set by resize.

Input Schema

NameRequiredDescriptionDefault
tabNoTab id from tabs_list. Defaults to the current tab.
pathNoFile path to also save the PNG to, e.g. out/page.png (parent folders are created). Omit to only return the image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / path / description
      Previous value: -"File path to save the PNG to."New value: +"File path to also save the PNG to, e.g. out/page.png (parent folders are created). Omit to only return the image."
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint/openWorldHint, and the description adds real value: the image is returned inline, capture is viewport-limited (not full-page), size is determined by the viewport set through resize, and path triggers folder creation plus a saved path in the result. That folder-creating side effect is the one behavior worth flagging more loudly since it is a filesystem write, but it is at least disclosed.

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?

One tight paragraph, front-loaded with the action, with no filler sentences. Dense nested parentheticals (the full-page caveat and the path clause) make it slightly less scannable than it could be split into bullets.

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?

For a simple two-param capture tool with no output schema, the description covers what is returned (inline PNG), the limitation (viewport only), the reload/scroll workaround, the resize dependency, and the optional save result. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so both parameters are already documented, including the 'Tab id from tabs_list, defaults to current tab' and the path/parent-folder semantics. The description restates the path behavior and default size source rather than adding new meaning, so baseline 3 is appropriate.

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?

States a concrete verb and resource ('capture the visible viewport of a tab as a PNG image') and immediately scopes it against siblings by saying snapshot and get_text only describe structure and text. An agent knows exactly what this returns and how it differs from the other read tools.

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?

Names the selection condition explicitly: use this for visual layout, colours or images, because snapshot/get_text are text/structural. It also states the negative case (full-page capture unsupported; scroll and capture again) and the optional save flow, leaving no routing ambiguity.

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

Deploy Server

Other Tools