Skip to main content
Glama
upnorthmedia

Screenshot MCP

by upnorthmedia

list_device_presets

Retrieve available device configurations for responsive website screenshot capture, enabling selection of specific screen sizes and settings.

Instructions

List available device presets with their configurations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'list_device_presets' tool. It processes the DEVICE_PRESETS constant, formats it into a readable list, and returns it as text content.
    case 'list_device_presets':
      const presetsList = Object.entries(DEVICE_PRESETS).map(([name, config]) => ({
        name,
        ...config
      }));
    
      return {
        content: [
          {
            type: 'text',
            text: 'Available device presets:\n\n' + 
                  presetsList.map(preset => 
                    `**${preset.name}**\n` +
                    `- Dimensions: ${preset.width}x${preset.height}\n` +
                    `- Scale: ${preset.deviceScaleFactor}x\n` +
                    `- Mobile: ${preset.isMobile}\n` +
                    `- Touch: ${preset.hasTouch}\n`
                  ).join('\n')
          }
        ]
      };
  • Input schema for the 'list_device_presets' tool, which takes no parameters.
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false
    }
  • index.js:167-175 (registration)
    Registration of the 'list_device_presets' tool in the tools array used for ListToolsRequest.
    {
      name: 'list_device_presets',
      description: 'List available device presets with their configurations',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false
      }
    }
  • DEVICE_PRESETS constant that provides the device configurations listed by the tool handler.
    export const DEVICE_PRESETS = {
      mobile: {
        width: 375,
        height: 667,
        deviceScaleFactor: 2,
        isMobile: true,
        hasTouch: true,
        userAgent: 'Mozilla/5.0 (iPhone; CPU iPhone OS 14_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0 Mobile/15A372 Safari/604.1'
      },
      tablet: {
        width: 768,
        height: 1024,
        deviceScaleFactor: 2,
        isMobile: true,
        hasTouch: true,
        userAgent: 'Mozilla/5.0 (iPad; CPU OS 14_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0 Mobile/15A372 Safari/604.1'
      },
      desktop: {
        width: 1920,
        height: 1080,
        deviceScaleFactor: 1,
        isMobile: false,
        hasTouch: false,
        userAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36'
      }
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions listing 'available device presets with their configurations,' which implies a read-only operation, but doesn't specify whether this requires authentication, how results are returned (e.g., pagination, format), or any rate limits. This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, clear sentence that directly states the tool's purpose without any fluff or redundant information. It is front-loaded and efficiently communicates the essential action, making it highly concise and well-structured.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate as a basic read operation. However, it lacks details on output format, authentication needs, or error handling, which could be important for an agent. It meets the minimum viable standard but has clear gaps in completeness.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, meaning no parameters are defined. The description doesn't need to add parameter details, so it appropriately avoids redundancy. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce unnecessary complexity.

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 states the action ('List') and the resource ('device presets with their configurations'), making the purpose immediately understandable. It doesn't differentiate from sibling tools (capture_element, capture_screenshot), which are unrelated capture operations, so it doesn't reach the highest score for sibling differentiation.

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 or in what context. It simply states what the tool does without indicating prerequisites, timing, or comparisons to other tools, leaving the agent with no usage direction.

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/upnorthmedia/ScreenshotMCP'

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