Skip to main content
Glama

responsive_screenshots

Capture screenshots at mobile, tablet, and desktop viewports to review responsive design. Enter a URL to generate visual comparisons across device sizes.

Instructions

Capture screenshots at mobile (375px), tablet (768px), and desktop (1440px) viewports. Perfect for reviewing responsive design.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the page to capture

Implementation Reference

  • The actual implementation of the captureResponsiveScreenshots function, which orchestrates capturing screenshots at multiple viewport sizes.
    export async function captureResponsiveScreenshots(
      url: string
    ): Promise<readonly ScreenshotResult[]> {
      const viewports = [
        { width: 375, height: 812, label: "mobile" },
        { width: 768, height: 1024, label: "tablet" },
        { width: 1440, height: 900, label: "desktop" },
      ] as const;
    
      const results: ScreenshotResult[] = [];
    
      for (const viewport of viewports) {
        const result = await captureScreenshot({
          url,
          width: viewport.width,
          height: viewport.height,
          fullPage: true,
          delay: 1000,
          deviceScaleFactor: 2,
        });
        results.push(result);
      }
    
      return results;
    }
  • src/server.ts:306-325 (registration)
    The registration of the 'responsive_screenshots' tool in the MCP server.
    server.tool(
      "responsive_screenshots",
      "Capture screenshots at mobile (375px), tablet (768px), and desktop (1440px) viewports. Perfect for reviewing responsive design.",
      {
        url: z.string().url().describe("URL of the page to capture"),
      },
      async ({ url }) => {
        try {
          const results = await captureResponsiveScreenshots(url);
          const labels = ["Mobile (375px)", "Tablet (768px)", "Desktop (1440px)"];
    
          const content = results.flatMap((result, i) => [
            {
              type: "text" as const,
              text: `### ${labels[i]}`,
            },
            {
              type: "image" as const,
              data: result.base64,
              mimeType: result.mimeType,
Behavior2/5

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

With no annotations provided, the description carries full behavioral burden. It discloses the specific viewport widths (375/768/1440px) but fails to document critical execution details: return format (file paths vs base64 images?), output quantity (3 separate files?), execution time, or error conditions (timeouts, invalid URLs).

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?

Two sentences with zero waste: the first defines the core action and technical specifics, the second provides the use-case context. Information is front-loaded and appropriately sized for a single-parameter tool.

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?

Despite the simple 1-parameter schema, the description is incomplete because no output schema exists and the description omits return value semantics (image format, delivery method). For a media-generation tool, missing output specifications create significant ambiguity in how to handle results.

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 coverage is 100% with the 'url' parameter fully documented as 'URL of the page to capture.' The description adds no additional parameter semantics (e.g., protocol requirements, authentication via URL), warranting the baseline score of 3 for high-coverage schemas.

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

Purpose5/5

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

Excellent specificity: 'Capture screenshots' provides the verb and resource, while 'mobile (375px), tablet (768px), and desktop (1440px)' precisely defines scope. This clearly distinguishes it from the sibling 'screenshot' tool by specifying multiple viewport widths.

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?

Provides implied context with 'Perfect for reviewing responsive design,' indicating appropriate use cases. However, it lacks explicit when-not-to-use guidance or direct comparison to the sibling 'screenshot' tool (e.g., 'Use this instead of screenshot when you need multiple breakpoints').

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/prembobby39-gif/uimax-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server