Skip to main content
Glama
Mobile Next MCP Server

Mobile Next MCP Server

Official
by mobile-next

Take Screenshot

mobile_take_screenshot
Read-only

Captures a mobile device screenshot to inspect the current screen and convert screenshot positions into screen coordinates before tapping. Do not cache the result.

Instructions

Take a screenshot of the mobile device. Use this to understand what's on screen, if you need to press an element that is available through view hierarchy then you must list elements on screen instead. The screenshot is usually smaller than the screen, so when the device reports its screen size the result also states how to convert positions in the screenshot into screen coordinates before tapping. Do not cache this result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "device": "<device>"
    },
    "name": "mobile_take_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipNoOnly capture this region of the screen, in screen coordinates (the ones used for tapping). Applied before maxSize/scale. Use it to look at one part of the screen in more detail or at a lower cost.
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.
maxSizeNoMaximum width/height in pixels, keeping aspect ratio. Defaults to 1024.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.18
    • addedInput schema / properties / clip
      Added value: +{
      +  "description": "Only capture this region of the screen, in screen coordinates (the ones used for tapping). Applied before maxSize/scale. Use it to look at one part of the screen in more detail or at a lower cost.",
      +  "properties": {
      +    "height": {
      +      "description": "Height of the region",
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    },
      +    "width": {
      +      "description": "Width of the region",
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    },
      +    "x": {
      +      "description": "Left edge of the region",
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    "y": {
      +      "description": "Top edge of the region",
      +      "minimum": 0,
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "x",
      +    "y",
      +    "width",
      +    "height"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv1.0.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changedv1.0.3
    • addedInput schema / properties / maxSize
      Added value: +{
      +  "description": "Maximum width/height in pixels, keeping aspect ratio. Defaults to 1024.",
      +  "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"
      +}
  4. Changed4 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"
      +}
    • removedInput schema / properties / noParams
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {},
      -  "type": "object"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "noParams"
      -]New value: +[
      +  "device"
      +]
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already provided, the description adds useful behavioral context beyond annotations: the screenshot is usually smaller than the device screen, the result explains coordinate conversion for tapping, and the result should not be cached. It does not describe the exact return format, but the key operational caveats are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the action and use case, then adds coordinate and caching caveats. It contains minor wordiness in the view-hierarchy sentence, but every sentence contributes relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only screenshot tool with no output schema, the description explains the primary use case, an alternative path for element interaction, coordinate conversion behavior, and caching guidance. It is sufficiently complete, though it could mention the returned image format or whether output is an image object.

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 clip, scale, maxSize, and device are already documented in the schema. The description adds coordinate-system context relevant to screenshots but does not deepen parameter-specific semantics beyond what the schema provides, which aligns with the baseline 3 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 states a specific verb and resource: 'Take a screenshot of the mobile device.' It partially distinguishes from siblings by naming mobile_list_elements_on_screen as the alternative when interacting with view-hierarchy elements, though it does not clarify how it differs from mobile_save_screenshot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear when-to-use guidance ('to understand what's on screen') and an explicit when-not/alternative case ('if you need to press an element... you must list elements on screen instead'). It lacks coverage of other screenshot-related siblings such as saving, but the core routing guidance is present.

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