Skip to main content
Glama

tab_screenshot

Capture an image of a tab's visible area to inspect visual layout such as charts, images, styling, or canvas apps. Makes the tab active first and returns the screenshot as an attachment.

Instructions

Take a screenshot of the visible part of a tab in the user's browser, returned as an image attachment. The tab is made active in its window first. Use it when the visual layout matters (charts, images, styling, canvas apps); for text and controls, tab_read is cheaper and gives refs to act on. On a canvas page, click what it shows with tab_click x and y: the result gives the viewport size in CSS pixels to scale image pixels by.

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": "tab_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab id from tab_list or tab_read. Defaults to the active tab of the browser window the user used last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose key behavior: the tab is made active in its window first (a real state side effect), the result is an image attachment, and viewport size is reported in CSS pixels for pixel-to-coordinate scaling. It stops short of failure modes or what happens with tabs in other windows/minimized windows, so it is strong but not exhaustive.

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?

Four sentences, all substantive, with the core action and return form front-loaded before the alternative and the canvas follow-up. It is dense but not padded; the final sentence on scaling could arguably be split for readability, but nothing is wasted.

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 one-optional-parameter screenshot tool with no output schema and no annotations, the description covers action, side effects, return type, sibling routing, and the coordinate-scaling detail an agent needs to act on the image. Nothing essential 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% and the single tabId parameter is already fully documented, including its default. The description adds no parameter-level meaning beyond that, so baseline 3 applies; the coordinate-scaling note concerns the return value rather than the input.

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 specific verb and resource ('take a screenshot of the visible part of a tab'), including the scope limit (visible part) and the return form (image attachment). It also distinguishes itself from the closest sibling, tab_read, so an agent can choose between them without opening either schema.

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?

Explicitly gives the when-to-use condition ('when the visual layout matters - charts, images, styling, canvas apps') and the alternative with its tradeoff ('for text and controls, tab_read is cheaper and gives refs to act on'). It goes further and explains the follow-up pattern on canvas pages via tab_click x and y, leaving little to inference.

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