Skip to main content
Glama

capture_responsive_screens

Capture browser screenshots across a chosen matrix of viewport widths and heights, saving them to an output directory for responsive layout review.

Instructions

Capture an explicitly chosen responsive viewport matrix.

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": {
      "url": "<url>",
      "outputDirectory": "<outputDirectory>"
    },
    "name": "capture_responsive_screens"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
heightNo
widthsNo
outputDirectoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and non-idempotency, so the safety profile is covered. The description adds nothing beyond that — it never says that files are written to disk, where they land relative to outputDirectory, whether capture waits for rendering, or how many images are produced per request.

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?

It is a single front-loaded sentence with no wasted words, but the brevity comes at the cost of under-specification rather than efficiency. There is no structure beyond the one clause to organize the usage or behavior information.

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?

An output schema exists, so return values need not be explained, but for a four-parameter capture tool that writes files, the definition is far too thin. Neither the viewport semantics nor the output destination, which is a required parameter, is addressed anywhere.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, including the required outputDirectory. The phrase 'explicitly chosen' hints at the widths array but gives no defaults, bounds, or meaning for height versus widths, and says nothing about what outputDirectory must be or whether it is created.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Capture') and a resource ('responsive viewport matrix'), which suggests screenshots across multiple viewport sizes. However, 'matrix' and 'explicitly chosen' are jargon that leaves the actual output (a set of images at each width) implicit, and it does not distinguish this from siblings such as capture_page or capture_user_flow.

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 guidance on when to pick this over capture_page or capture_user_flow, and no prerequisites are stated (e.g., whether the capture environment must be prepared first). An agent must infer the choice purely from the name.

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