Skip to main content
Glama
Nam0101

android-mcp-toolkit

Dump UI Hierarchy (XML)

dump-ui-hierarchy

Capture the current Android UI hierarchy as XML using UIAutomator for analysis and debugging.

Instructions

Capture the current UI hierarchy as XML using uiautomator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeoutMsNoTimeout in milliseconds

Implementation Reference

  • The async handler that executes 'dump-ui-hierarchy': runs uiautomator dump on device, cats the result, and returns it as text content.
    async (params) => {
      const devicePath = '/data/local/tmp/mcp_window_dump.xml';
      await runAdbCommand(['shell', 'uiautomator', 'dump', devicePath], params.timeoutMs);
      const content = await runAdbCommand(['shell', 'cat', devicePath], params.timeoutMs);
      return { content: [{ type: 'text', text: content.trim() }] };
    }
  • Input schema for dump-ui-hierarchy: optional timeoutMs (1-20s, default 10s).
    const dumpUiSchema = z.object({
      timeoutMs: z.number().int().min(1000).max(20000).default(10000).describe('Timeout in milliseconds')
    });
  • Registration of the 'dump-ui-hierarchy' tool on the MCP server via registerDeviceTool().
    server.registerTool(
      'dump-ui-hierarchy',
      {
        title: 'Dump UI Hierarchy (XML)',
        description: 'Capture the current UI hierarchy as XML using uiautomator.',
        inputSchema: dumpUiSchema
      },
      async (params) => {
        const devicePath = '/data/local/tmp/mcp_window_dump.xml';
        await runAdbCommand(['shell', 'uiautomator', 'dump', devicePath], params.timeoutMs);
        const content = await runAdbCommand(['shell', 'cat', devicePath], params.timeoutMs);
        return { content: [{ type: 'text', text: content.trim() }] };
      }
    );
  • src/index.js:30-30 (registration)
    Top-level call that registers deviceTool (including dump-ui-hierarchy) on the MCP server.
    registerDeviceTool(server);
Behavior2/5

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

With no annotations, the description bears full burden. It only states the action but does not disclose side effects, permissions, or if the UI is disrupted. No mention of requirements like accessibility service.

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?

Single sentence with no extraneous words. Could benefit from slight structural expansion but is efficient.

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?

Given the simplicity (one optional param, no output schema), the description is too minimal. It omits what the XML contains, return format, or any limitations, leaving gaps for an agent.

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% with a well-described timeout parameter (default, min, max). The description adds nothing beyond the schema, leaving baseline at 3.

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 clearly states the verb 'Capture', the resource 'current UI hierarchy', and the format 'XML', using 'uiautomator'. It distinguishes from siblings like 'get-current-activity' (activity vs hierarchy) and 'take-screenshot' (visual vs structural).

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 (e.g., when to dump hierarchy vs take a screenshot or get current activity). Missing information about preconditions or context.

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/Nam0101/android-mcp-toolkit'

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