Skip to main content
Glama

browser_screenshot

browser_screenshot
Read-onlyIdempotent

Capture an image of a Chrome tab, including background tabs, when page layout or visual state matters. Use it instead of describing a page in text.

Instructions

Capture a screenshot of a Chrome tab as an image. Works on a background tab. Prefer this over describing a page in text when layout or visual state matters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tab_id": "<tab_id>"
    },
    "name": "browser_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipNo
tab_idYesChrome tab ID.
full_pageNo
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
image_formatNo
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact: it works on a background tab, meaning the tab need not be focused. It says nothing about what the call returns (image payload shape), size limits, or how session ownership affects the capture.

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?

Three short sentences, front-loaded with the core action, then the background-tab caveat, then the selection rule. No filler and no repetition of the title.

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?

Adequate for a simple capture tool, but with no output schema and half the parameters undocumented, an agent cannot tell from the definition what a full_page or clipped capture yields, or what image_format defaults to. Explaining the clip/full_page/image_format interplay would close the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% and the description mentions no parameters at all. clip, full_page, and image_format have no description in either the schema or the prose, leaving three of six parameters unexplained. The nested clip object in particular would benefit from a note about coordinate units and scale behavior.

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?

States a specific verb and resource ("Capture a screenshot of a Chrome tab as an image") and names the output medium. Sibling differentiation is only implied via "describing a page in text" rather than naming browser_get_page_content or browser_observe, so it falls just short of a 5.

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

Usage Guidelines4/5

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

Gives a clear selection rule: prefer this over textual description when layout or visual state matters. There is no explicit when-not guidance (e.g., avoid for pure DOM/text extraction where cheaper tools suffice), so it is good but not exhaustive.

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