Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic

screenshot

Capture a screenshot of the current webpage using AutoProbeMCP. Optional full-page or custom save path support for flexible usage in browser automation tasks.

Instructions

Take a screenshot of the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullPageNoCapture full scrollable page
pathNoPath to save screenshot (optional)

Implementation Reference

  • Handler for the 'screenshot' tool: validates args with ScreenshotSchema, captures screenshot of current page using Playwright (fullPage and path options), returns success message with buffer size or save path.
    case 'screenshot': {
      if (!currentPage) {
        throw new Error('No browser page available. Launch a browser first.');
      }
    
      const params = ScreenshotSchema.parse(args);
      const buffer = await currentPage.screenshot({
        fullPage: params.fullPage,
        path: params.path
      });
    
      const result = params.path 
        ? `Screenshot saved to: ${params.path}`
        : `Screenshot captured (${buffer.length} bytes)`;
    
      return {
        content: [
          {
            type: 'text',
            text: result
          }
        ]
      };
    }
  • Zod schema for 'screenshot' tool inputs: fullPage (boolean, default false), path (optional string to save screenshot).
    const ScreenshotSchema = z.object({
      fullPage: z.boolean().default(false),
      path: z.string().optional()
    });
  • src/index.ts:219-236 (registration)
    Tool registration in ListToolsResponse: defines name 'screenshot', description, and inputSchema matching the Zod schema.
    {
      name: 'screenshot',
      description: 'Take a screenshot of the current page',
      inputSchema: {
        type: 'object',
        properties: {
          fullPage: {
            type: 'boolean',
            default: false,
            description: 'Capture full scrollable page'
          },
          path: {
            type: 'string',
            description: 'Path to save screenshot (optional)'
          }
        }
      }
    },
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. It states the action but lacks behavioral details such as whether it requires specific permissions, what happens if no path is provided (e.g., default save location), error handling for invalid paths, or if it blocks until completion. This leaves 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, efficient sentence with zero waste. It is front-loaded with the core action and target, making it easy to grasp immediately without unnecessary elaboration.

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?

Given the tool's moderate complexity (involving browser interaction and file output), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, output format (e.g., image type), or dependencies on other tools (e.g., requiring 'launch_browser' first), leaving significant gaps for an agent.

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 the schema already documents both parameters ('fullPage' and 'path') with clear descriptions. The description adds no additional meaning beyond implying a screenshot is taken, which is redundant with the tool name. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('Take a screenshot') and the target ('current page'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'analyze_screenshot' or 'get_page_info', which might be relevant alternatives for different use cases.

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. For example, it doesn't mention when to prefer 'screenshot' over 'get_page_info' for visual capture or 'analyze_screenshot' for post-processing, nor does it specify prerequisites like needing an active browser session.

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

Related 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/Wladastic/AutoProbeMCP'

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