Skip to main content
Glama

screenshot

Capture a tab's visible viewport as an image so its pixel positions can guide click, hover, and scroll actions.

Instructions

Take a screenshot of the tab's visible viewport. Pixel positions in the image are the coordinates click/hover/scroll accept.

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": {
      "tabId": "<tabId>"
    },
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab ID, from tabs_list or tab_create

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one meaningful trait: only the visible viewport is captured, not the full page. It says nothing about the return payload form (image blob vs. URL), behavior on background tabs, or whether overlays/annotations are included in 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?

Two short sentences, no filler. The scoping constraint leads, and the coordinate-mapping hint follows as a downstream integration note — each sentence earns its place.

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 one-parameter tool with no output schema, the definition covers purpose, scope, and the practical reason to call it (coordinate space for click/hover/scroll). The main residual gap is the return format, which is implied by the name but never stated, and any note on background-tab behavior.

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?

The single tabId parameter is fully documented in the schema (100% coverage) including its source (tabs_list or tab_create), so the schema does the work. The description adds no additional meaning about the parameter, which is acceptable at this coverage level but not a value-add.

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') and immediately bounds the scope to the 'tab's visible viewport', which is the key distinction an agent needs to tell it apart from text-extraction siblings like read_page or get_page_text.

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

Usage Guidelines3/5

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

The second sentence implies when to reach for this tool — you need pixel coordinates for click/hover/scroll — which is genuinely useful implied guidance. However, there is no explicit when-not condition and no named alternative for cases like 'I need the page's text instead', leaving the agent to infer routing.

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