Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Take Screenshot

mobile_take_screenshot
Read-only

Capture a screenshot of a mobile device to see what's on screen. The result includes coordinate conversion details for accurate tapping.

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.

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.
maxSizeNoMaximum width/height in pixels, keeping aspect ratio. Defaults to 1024.

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. 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"
+}
  2. 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"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=true, which say nothing about the mechanics of the result. The description adds two non-obvious behavioral facts: the screenshot is usually smaller than the screen, and the result includes coordinate-conversion guidance needed before tapping, plus a caching warning. That is substantial context beyond the structured fields.

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?

Front-loads the core action in the first sentence and follows with the routing rule and the coordinate/caching caveats. Every sentence carries information, though the coordinate-conversion sentence is dense and could be split; minor stylistic drag.

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?

No output schema exists, and the description covers what the agent actually needs from the return value (that it states how to map screenshot positions to screen coordinates). It stops short of describing the image encoding/size defaults, but those are covered by the schema and are not essential to correct invocation.

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 scale, device, and maxSize are already fully documented in the schema, including the interaction between scale and maxSize. The description adds no parameter-level detail, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Take a screenshot of the mobile device') and immediately distinguishes itself from the element-listing sibling by naming the exact condition that selects that alternative. An agent can tell it apart from mobile_list_elements_on_screen and mobile_save_screenshot without opening the schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('understand what's on screen'), explicit alternative routing ('if you need to press an element ... you must list elements on screen instead'), and an explicit prohibition ('Do not cache this result'). This is exactly the when/when-not/alternatives structure the dimension rewards.

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