Skip to main content
Glama

真实截图(需用户授权一次)

get_screenshot

Capture real rendered pixels from a browser page, optionally cropped to a specific element. Use when true visual output is needed for canvas, images, or occlusion checks; requires one-time user authorization per page load.

Instructions

通过浏览器屏幕捕获(getDisplayMedia)截取真实渲染像素并返回图片。首次调用会在用户浏览器弹出原生授权框(预选当前标签页),用户授权一次后本次页面生命周期内免打扰;页面刷新后需重新授权。传 selector 时按该元素矩形裁剪(深度查询,穿 shadow DOM)。验证颜色/布局/定位请优先用 get_dom_snapshot(文本、免授权、精确到值);本工具用于需要真实像素的场景(canvas、图片、遮挡观感)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo操作说明:展示给页面用户的自然语言描述(用户会在页面气泡的操作记录里看到),用用户的语言填写,建议始终提供
pageIdNo目标页面 id(单页时可省略)
selectorNo可选:只截取该元素(深度查询),不传则截整个视口
timeoutMsNo超时毫秒数,默认 60000(首次调用要等用户在浏览器里点授权)
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly explains the authorization prompt, one-time approval per page lifecycle, re-authorization after refresh, selector deep-query behavior through shadow DOM, and timeout implications.

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 dense but every sentence earns its place: core function, authorization side-effect, selector behavior, and alternative tool guidance. It is front-loaded with the most important 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?

The description is complete for a screenshot tool with 4 parameters and no output schema. It covers purpose, side effects, usage conditions, selector semantics, timeout behavior, and alternative tool routing. Nothing essential is missing.

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 100%, so the baseline is 3. The description adds useful context beyond the schema, such as selector cropping behavior and why timeoutMs matters on first call, elevating it slightly.

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 identifies the tool's specific function: capturing real rendered pixels via getDisplayMedia and returning an image. It also distinguishes itself from get_dom_snapshot, making the tool's unique niche immediately understandable.

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 explicitly states when to prefer get_dom_snapshot (color/layout/position verification via text) and when to use this tool (real pixel needs like canvas, images, occlusion). This provides clear routing guidance relative to siblings.

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/kirakiray/web-bridge-mcp'

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