Skip to main content
Glama

Set Orientation

mobile_set_orientation
Destructive

Change mobile device screen orientation between portrait and landscape modes for automated testing or accessibility adjustments.

Instructions

Change the screen orientation of the device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.
orientationYesThe desired orientation

Implementation Reference

  • Handler function for the mobile_set_orientation tool. Ensures a device is selected via requireRobot() and delegates to the Robot instance's setOrientation method.
    async ({ orientation }) => {
    	requireRobot();
    	await robot!.setOrientation(orientation);
    	return `Changed device orientation to ${orientation}`;
    }
  • Zod input schema for the tool, defining 'orientation' as enum ['portrait', 'landscape'].
    orientation: z.enum(["portrait", "landscape"]).describe("The desired orientation"),
  • src/server.ts:451-462 (registration)
    Registration of the mobile_set_orientation tool on the MCP server using the 'tool' helper.
    tool(
    	"mobile_set_orientation",
    	"Change the screen orientation of the device",
    	{
    		orientation: z.enum(["portrait", "landscape"]).describe("The desired orientation"),
    	},
    	async ({ orientation }) => {
    		requireRobot();
    		await robot!.setOrientation(orientation);
    		return `Changed device orientation to ${orientation}`;
    	}
    );
  • Android-specific helper: AndroidRobot.setOrientation sets accelerometer_rotation to 0 and user_rotation to 0 (portrait) or 1 (landscape) via adb.
    public async setOrientation(orientation: Orientation): Promise<void> {
    	const orientationValue = orientation === "portrait" ? 0 : 1;
    
    	// disable auto-rotation prior to setting the orientation
    	this.adb("shell", "settings", "put", "system", "accelerometer_rotation", "0");
    	this.adb("shell", "content", "insert", "--uri", "content://settings/system", "--bind", "name:s:user_rotation", "--bind", `value:i:${orientationValue}`);
    }
  • iOS-specific helper: WebDriverAgent.setOrientation sends POST to /orientation endpoint with orientation in uppercase within a session.
    public async setOrientation(orientation: Orientation): Promise<void> {
    	await this.withinSession(async sessionUrl => {
    		const url = `${sessionUrl}/orientation`;
    		await fetch(url, {
    			method: "POST",
    			headers: { "Content-Type": "application/json" },
    			body: JSON.stringify({
    				orientation: orientation.toUpperCase()
    			})
    		});
    	});
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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: -[
      -  "orientation"
      -]New value: +[
      +  "device",
      +  "orientation"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior2/5

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

The description adds no behavioral context beyond what annotations already indicate (destructiveHint=true). It does not disclose side effects, reversibility, or any device-specific behavior. Given that this is a mutating operation, more transparency would be valuable, but the annotation covers the basic destructive nature.

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, clear, front-loaded sentence with no filler. It efficiently states the action and target resource, earning a high score for conciseness.

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 simple tool with two well-documented parameters and no output schema, the description and schema provide sufficient information. The only minor gap is the lack of usage guidance, but overall the definition is complete enough for its complexity.

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 coverage is 100% and both parameters are fully described, including the enum values for orientation. The description adds no extra parameter semantics, so the baseline of 3 is appropriate.

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?

The description uses a specific verb ('Change') and a clear resource ('screen orientation'), making the tool's purpose unambiguous. It naturally distinguishes from sibling mobile_get_orientation, which reads orientation rather than changing it.

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

Usage Guidelines3/5

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

The description implies a setter role opposite to mobile_get_orientation, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or side effects. Usage context is only inferred from the verb 'change' and the sibling tool name.

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