Skip to main content
Glama
Sign In
jev-reach

jev-reach

by rashedInt32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

take_screenshot

Capture a web page or element screenshot after Jev navigates to the desired state, with options for format, quality, and full-page capture.

Instructions

Take a screenshot of the page or element.

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

Input Schema

NameRequiredDescriptionDefault
uidNoThe uid of an element on the page from the page content snapshot. If omitted, takes a page screenshot.
formatNoType of format to save the screenshot as. Default is "png"png
pageIdYesTargets a specific page by ID.
qualityNoCompression quality for JPEG and WebP formats (0-100). Higher values mean better quality but larger file sizes. Ignored for PNG format.
filePathNoThe absolute path, or a path relative to the current working directory, to save the screenshot to instead of attaching it to the response.
fullPageNoIf set to true takes a screenshot of the full page instead of the currently visible viewport. Incompatible with uid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The description only states the core action and target, adding little beyond the annotations. It does not disclose behavior such as whether the screenshot is attached to the response or saved to a file when filePath is provided, nor does it mention fullPage incompatibilities. These are left to the schema, not the description.

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?

The description is a single concise sentence with no wasted words, making it easy to parse. It is not structured with additional details, but for a simple tool this brevity is appropriate and front-loads the primary purpose.

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?

The schema is rich and describes all six parameters clearly, which compensates for the minimal description. However, there is no mention of what the tool returns or how screenshots are delivered when filePath is not used, and no guidance on element vs page screenshot distinctions. This leaves some gaps, but the schema covers most operational details.

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%, so the schema already thoroughly documents each parameter. The description adds no additional meaning about parameters; it merely mentions 'page or element,' which is already reflected in the pageId and uid parameter descriptions. A baseline 3 is appropriate since the schema carries the semantic load.

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?

The description clearly identifies the operation ('Take a screenshot') and the target ('the page or element'), which is specific and understandable. However, it does not differentiate itself from sibling tools like take_snapshot or take_heapsnapshot, so an agent might not know which capture tool to select without more context.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. There is no reference to performance traces, snapshots, or other capture mechanisms, so the agent is left without context for choosing this specific tool.

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