Skip to main content
Glama

screenshot

Capture a PNG of the current viewport or a specific element, with optional annotation of element IDs for visual debugging.

Instructions

PNG of viewport or element; annotate labels ids.

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
idNo
annotateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and delivers very little. It states the format (PNG) and the two framings, but says nothing about whether the page is mutated, how the image is returned/sized, or what "annotate" actually draws. The trailing "annotate labels ids" is too compressed to convey behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Eight words with the key noun (PNG) front-loaded, so nothing is wasted, but the second clause is telegraphic to the point of ambiguity rather than being genuinely concise. Brevity here costs comprehension.

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 2-parameter, annotation-free tool with no output schema, the description should at minimum clarify how the image is returned and what annotate produces. Format and capture scope are covered, but the parameter behavior and the relationship to sibling capture tools are not.

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

Parameters4/5

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

Schema description coverage is 0% for both params, yet the description does gesture at both: "viewport or element" implies the id/selector targets an element, and "annotate" names the boolean's effect. The phrasing "annotate labels ids" is cryptic about what gets labeled, but it does more than the empty schema does, so above the missing-parameter baseline is warranted while stopping short of a top score.

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?

"PNG of viewport or element" names a concrete output format and both capture scopes (full viewport vs. a specific element), which is enough to know this takes a picture. It does not distinguish itself from the sibling "snapshot" tool, so an agent cannot confidently choose between them from this text alone.

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?

There is no when-to-use guidance, no exclusion of alternatives, and no prerequisites (e.g., page must be opened first). The word "snapshot" among the siblings makes the absence of any differentiating guidance more costly, but no guidance at all is offered here.

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

Deploy Server

Other Tools