Skip to main content
Glama

Save Screenshot

mobile_save_screenshot
Destructive

Capture and save screenshots from mobile devices for automation testing and debugging purposes. Specify device identifier and file path to store the image.

Instructions

Save a screenshot of the mobile device to a file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.
saveToYesThe path to save the screenshot to

Implementation Reference

  • src/server.ts:384-397 (registration)
    Registration of the 'mobile_save_screenshot' tool, including input schema (saveTo path) and inline handler that uses the selected robot to capture and save a screenshot to the specified file path.
    tool(
    	"mobile_save_screenshot",
    	"Save a screenshot of the mobile device to a file",
    	{
    		saveTo: z.string().describe("The path to save the screenshot to"),
    	},
    	async ({ saveTo }) => {
    		requireRobot();
    
    		const screenshot = await robot!.getScreenshot();
    		fs.writeFileSync(saveTo, screenshot);
    		return `Screenshot saved to: ${saveTo}`;
    	}
    );
  • The handler function for 'mobile_save_screenshot' is defined inline during registration. It requires a selected robot/device, captures the screenshot buffer via robot.getScreenshot(), and writes it synchronously to the filesystem using fs.writeFileSync.
    tool(
    	"mobile_save_screenshot",
    	"Save a screenshot of the mobile device to a file",
    	{
    		saveTo: z.string().describe("The path to save the screenshot to"),
    	},
    	async ({ saveTo }) => {
    		requireRobot();
    
    		const screenshot = await robot!.getScreenshot();
    		fs.writeFileSync(saveTo, screenshot);
    		return `Screenshot saved to: ${saveTo}`;
    	}
    );
  • Input schema for 'mobile_save_screenshot' tool: requires a 'saveTo' string parameter specifying the file path.
    saveTo: z.string().describe("The path to save the screenshot to"),
Behavior3/5

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

Annotations provide destructiveHint=true, indicating this tool performs a destructive operation (likely writing a file). The description adds that it saves to a file, which aligns with the destructive hint but doesn't provide additional behavioral context such as file format, overwrite behavior, or error handling. No contradiction with annotations is present.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to understand quickly.

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 moderate complexity (destructive operation with two parameters) and lack of output schema, the description is minimally adequate. It covers the basic action but misses details like output format, error conditions, or differentiation from siblings, leaving gaps for the agent to infer.

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%, with clear descriptions for both parameters (device identifier and save path). The description doesn't add any semantic details beyond what the schema provides, such as file format expectations or device availability constraints, so it meets the baseline for high schema coverage.

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 ('Save a screenshot') and the resource ('mobile device to a file'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from 'mobile_take_screenshot' in the sibling list, which appears to be a similar functionality.

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?

No guidance is provided on when to use this tool versus alternatives like 'mobile_take_screenshot' or other mobile interaction tools. The description lacks context about prerequisites, timing, or exclusions, leaving the agent without 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/EmpathySlainLovers/MCP'

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