Skip to main content
Glama

screenshot

Read-only

Captures a screenshot of the visible area of a shared tab, bringing it to the front first so agents can see the current page state.

Instructions

Take a screenshot of the visible part of a shared tab. The tab is brought to the front first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds non-obvious behavior beyond that: the capture covers only the visible viewport, and the tab is activated/brought to front first, which is a side effect an agent should know about before calling during a multi-tab workflow.

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?

Two sentences, zero filler, with the scope constraint ('visible part') stated before the side effect ('brought to the front'). Nothing is redundant with the schema or annotations.

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?

For a single-parameter read-only tool this covers behavior well, but with no output schema the agent is never told what a screenshot call returns (image content, a file path, or a handle) or whether the fronting persists. That return-value gap is the main missing piece.

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%, and the single 'tab' parameter is fully documented in the schema including its format and the single-tab fallback, so the baseline is 3. The description only reinforces that the tab must be a shared one; it adds no format or selection detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource ('take a screenshot') plus a clear scope limitation ('visible part of a shared tab'), which tells an agent this is a viewport capture rather than a full-page or element capture. It doesn't name a sibling, but the purpose is unambiguous on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance, and no reference to alternatives such as read_text or list_tabs for cases where a visual capture is unnecessary. The usage is only inferable from the tool name and the 'shared tab' precondition.

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