Skip to main content
Glama

fl_screenshot

Captures screenshots of a browser tab or a single element by ref or selector when visual layout matters, returning CSS pixel coordinates usable for mouse actions.

Instructions

Screenshot of a tab, or of one element with ref / selector. Only when the visual layout matters: snapshots are much cheaper. Pixels are CSS pixels, usable as x / y for {do:"mouse"}.

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": "<tab>"
    },
    "name": "fl_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo
tabYes
fullNo
selectorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.1
    • addedInput schema / properties / ref
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / selector
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv1.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 burden and does add useful behavior: snapshots are cheaper, screenshot pixels are CSS pixels, and those coordinates are usable with mouse actions. It does not describe the return shape or what the 'full' option changes, but the core operational traits are disclosed.

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 compact clauses with no waste. The primary use case is front-loaded, followed by the key cost comparison and coordinate mapping detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read-only screenshot tool with no annotations or output schema, the description supplies the critical usage and coordinate semantics. It is not fully complete because the 'full' parameter and exact return form are not covered.

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 0%, so the description must compensate. It explains ref and selector as element targeting and implies tab as the screenshot target, but it does not explain the 'full' boolean parameter at all, leaving one of four parameters undocumented.

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 states a specific verb and resource: a screenshot of a tab or an element identified by ref/selector. It also distinguishes the tool from fl_snapshot by positioning snapshots as cheaper and screenshots as for visual layout.

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?

It gives explicit when-to-use guidance: only when visual layout matters, and contrasts that with snapshots being much cheaper. This routes the agent clearly between this tool and its likely alternative.

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