Skip to main content
Glama

pilot_responsive

Capture screenshots at mobile, tablet, and desktop viewport sizes to test responsive web design across multiple devices.

Instructions

Take screenshots at mobile (375x812), tablet (768x1024), and desktop (1280x720).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_prefixNoFile path prefix for screenshots

Implementation Reference

  • The handler for the 'pilot_responsive' tool, which takes screenshots at mobile, tablet, and desktop viewports.
    server.tool(
      'pilot_responsive',
      'Take screenshots at mobile (375x812), tablet (768x1024), and desktop (1280x720).',
      { output_prefix: z.string().optional().describe('File path prefix for screenshots') },
      async ({ output_prefix }) => {
        await bm.ensureBrowser();
        try {
          const page = bm.getPage();
          const prefix = output_prefix || path.join(TEMP_DIR, 'pilot-responsive');
          const viewports = [
            { name: 'mobile', width: 375, height: 812 },
            { name: 'tablet', width: 768, height: 1024 },
            { name: 'desktop', width: 1280, height: 720 },
          ];
          const originalViewport = page.viewportSize();
          const results: string[] = [];
    
          for (const vp of viewports) {
            await page.setViewportSize({ width: vp.width, height: vp.height });
            const filePath = `${prefix}-${vp.name}.png`;
            await page.screenshot({ path: filePath, fullPage: true });
            results.push(`${vp.name} (${vp.width}x${vp.height}): ${filePath}`);
          }
    
          if (originalViewport) await page.setViewportSize(originalViewport);
    
          return { content: [{ type: 'text' as const, text: results.join('\n') }] };
        } catch (err) {
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
Behavior3/5

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

Discloses the specific viewport dimensions (375x812, 768x1024, 1280x720) which is crucial behavioral context. However, with no annotations provided, it fails to disclose file naming patterns, whether viewports are restored after, overwrite behavior, or if the tool returns data URLs vs file paths.

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?

Extremely concise single sentence (9 words) with zero redundancy. The specific dimensions are front-loaded with the action verb, making every word high-value.

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?

Adequate for identifying the tool's unique capability, but leaves gaps regarding output behavior (file count, naming convention, format) and side effects on browser state given the lack of output schema or annotations.

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 has 100% description coverage for the single parameter. The description mentions 'screenshots' generally but adds no semantic detail about 'output_prefix' (e.g., how it constructs filenames, whether it appends device suffixes, or required path formats), meriting the baseline score.

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?

Clear specific action (take screenshots) with specific resource (viewport sizes) and exact dimensions. The mention of three specific breakpoints effectively distinguishes it from the sibling 'pilot_screenshot' tool.

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?

Implies usage for responsive design testing via the three viewport sizes, but provides no explicit when-to-use guidance, prerequisites (e.g., must navigate first), or explicit comparison to 'pilot_screenshot' for single-viewport needs.

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/TacosyHorchata/Pilot'

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