Skip to main content
Glama

test_responsiveness

Tests a webpage at mobile, tablet, and desktop viewport sizes to detect horizontal overflow, clipped content, broken navigation, overlapping elements, and capture screenshots for structured findings.

Instructions

Test a webpage across standard or custom viewport sizes (320px mobile to 1920px desktop). Detects horizontal overflow, clipped content, broken navigation, and overlapping elements at each size, captures screenshots, and returns structured findings.

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": "test_responsiveness"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to test. If omitted, tests the currently active page.
viewportsNoOptional custom viewports. Defaults to standard mobile, tablet, and desktop viewports.
settle_time_msNoWait time in ms for layout reflow (default: 400ms).
capture_screenshotsNoCapture and save screenshots for each viewport (default: true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior: what defects it detects, that it captures screenshots, and that it returns structured findings. It is silent on side effects (screenshots written to disk), runtime cost of sweeping many viewports, and whether it navigates away from the active page.

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?

A single dense sentence front-loads the action and scope, then lists detected defects and outputs. No filler, no repetition, and the size range is placed inline where it is most informative.

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 four-parameter, all-optional, read-only-in-spirit inspection tool with no output schema, the description gives enough to call it correctly: what it does, its default viewport coverage, and the shape of results ('structured findings'). The main residual gap is the absence of any statement about cost or side effects of screenshot capture.

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 all four parameters are documented in the schema itself, making 3 the baseline. The description adds the default viewport range (320px mobile to 1920px desktop), which usefully characterizes the default set, but adds nothing about viewports, settle_time_ms, or capture_screenshots beyond what the schema states.

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 names a specific verb and resource ('Test a webpage') and enumerates what the test covers: viewport sizes 320px-1920px, horizontal overflow, clipped content, broken navigation, overlapping elements, screenshots, structured findings. This distinguishes it from narrower siblings like detect_overflow or capture_screenshot, though it doesn't explicitly name those siblings to differentiate.

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?

Usage is implied by the description's scope: use it for a broad multi-viewport responsiveness sweep. It never states when to prefer narrower siblings such as detect_overflow, compare_viewports, or inspect_element_responsiveness, and gives no prerequisites (e.g., whether the page must be open first). The url parameter note ('tests the currently active page' if omitted) hints at context, but that is schema-level, not in the description.

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