Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Save Screenshot

mobile_save_screenshot

Capture a screenshot from a connected mobile device and save it to a specified file path, with optional scaling and size limits.

Instructions

Save a screenshot of the mobile device to a file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNoScale factor (0.0-1.0). Ignored if maxSize is provided.
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. Filename must end with .png, .jpg, or .jpeg
maxSizeNoMaximum width/height in pixels, keeping aspect ratio. Omit for full size.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.3
    • addedInput schema / properties / maxSize
      Added value: +{
+  "description": "Maximum width/height in pixels, keeping aspect ratio. Omit for full size.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / scale
      Added value: +{
+  "description": "Scale factor (0.0-1.0). Ignored if maxSize is provided.",
+  "exclusiveMinimum": 0,
+  "maximum": 1,
+  "type": "number"
+}
  2. Changed1 schema field changedv0.0.53
    • changedInput schema / properties / saveTo / description
      Previous value: -"The path to save the screenshot to"New value: +"The path to save the screenshot to. Filename must end with .png, .jpg, or .jpeg"
  3. Changed3 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / device
      Added value: +{
+  "description": "The device identifier to use. Use mobile_list_available_devices to find which devices are available to you.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "saveTo"
-]New value: +[
+  "device",
+  "saveTo"
+]
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description doesn't need to restate that. However, it adds no context about side effects, such as whether the file is overwritten, what permissions are required, or whether a new screenshot is captured. The description simply restates the obvious operation without revealing any behavioral nuances beyond what the annotations already convey.

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, concise sentence that immediately states the tool's purpose. It is front-loaded with the core action and avoids any filler or redundancy. Every word earns its place, making it an excellent example of conciseness.

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?

For a tool that saves a screenshot to a file, the description is incomplete. It doesn't explain what happens if the file already exists (overwrite vs. error), whether the tool captures a new screenshot or uses the current screen state, or any expected output. The lack of an output schema means the description should clarify the return value or success/failure indications, but it remains silent. Given the sibling tool mobile_take_screenshot, the distinction is unclear, and an agent might be uncertain about the exact behavior.

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 all four parameters are documented in the schema. The description adds no extra parameter-specific details beyond what the schema provides, such as how scale and maxSize interact (though the schema mentions scale is ignored if maxSize is provided). Since the schema covers everything, the description meets the baseline of 3.

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 states a clear verb and resource: 'Save a screenshot of the mobile device to a file.' This distinguishes it from sibling tools like mobile_get_screen_size or mobile_take_screenshot, though it doesn't explicitly differentiate itself from mobile_take_screenshot. The purpose is unambiguous and specific enough for an agent to understand the action.

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. Notably, there is a sibling tool mobile_take_screenshot, and the description doesn't clarify whether this tool captures a screenshot or saves an existing one, nor does it mention any prerequisites like prior screenshot capture or device availability. An agent must infer usage from the name and schema alone.

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

Deploy Server

Other Tools