Skip to main content
Glama

Take a screenshot

take_screenshot
Read-only

Take screenshot of the current page

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": {
      "sessionId": "<sessionId>"
    },
    "name": "take_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoImage formatpng
fullPageNoCapture full page or viewport only
sessionIdYesSession ID of the connected browser

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / sessionId / description
      Previous value: -"ID de sesión del navegador conectado"New value: +"Session ID of the connected browser"
    • changedInput schema / properties / type / description
      Previous value: -"Formato de imagen"New value: +"Image format"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. Beyond that the description only adds the word "current page"; it does not say how the image is delivered (inline data vs. saved file), whether an active session/navigation state is required, or what happens on failure, which matters for a tool with no output schema.

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?

A single short sentence with no wasted words and the key noun phrase front-loaded. It is efficient, though its brevity is close to under-specification rather than optimal density.

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

Completeness2/5

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

There is no output schema, so the description is the only place to explain that the tool returns image data and in what form (base64, file path, attachment). For a capture tool with three parameters and no documented return behavior, this leaves a significant gap an agent would notice at call time.

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 100%, with all three parameters including the png/jpeg enum and fullPage default documented inline. The description adds no meaning beyond the schema; the phrase "current page" does not clarify how fullPage interacts with viewport capture. Baseline 3 applies when the schema carries the parameter burden.

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?

"Take screenshot of the current page" names a specific verb (take screenshot) and resource (current page), so the agent knows exactly what action is performed. It does not explicitly differentiate from siblings like get_page_content or get_elements, which would be needed for 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 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 exclusions, and no reference to alternatives such as get_page_content for text extraction. The agent must infer that this tool is for visual capture from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources