Skip to main content
Glama

list_recordings

Retrieve all saved action recordings and macros for Android device automation through the Android MCP Server.

Instructions

List all saved action recordings/macros.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation logic for listing available recordings from the filesystem.
    listRecordings(): Array<{ filename: string; name: string; id: string; actionCount: number }> {
      const config = getConfig();
      const dir = config.recordingsDir;
    
      if (!existsSync(dir)) return [];
    
      return readdirSync(dir)
        .filter(f => f.endsWith('.json'))
        .map(filename => {
          try {
            const content = readFileSync(join(dir, filename), 'utf-8');
            const recording = JSON.parse(content) as Recording;
            return {
              filename,
              name: recording.name,
              id: recording.id,
              actionCount: recording.actions.length,
            };
          } catch {
            return null;
          }
        })
        .filter((r): r is NonNullable<typeof r> => r !== null);
    }
  • MCP tool registration for 'list_recordings'.
    server.registerTool(
      'list_recordings',
      {
        description: 'List all saved action recordings/macros.',
        inputSchema: {},
      },
      async () => {
        const recordings = actionRecorder.listRecordings();
        return {
          content: [{
            type: 'text' as const,
            text: JSON.stringify({ success: true, recordings }, null, 2),
          }],
        };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'List all' implies a safe read-only operation, but fails to disclose what 'all' encompasses (session vs. persistent storage), return format, or behavior when no recordings exist.

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?

Single efficient sentence with zero waste. Every word earns its place by identifying the action and target resource. Appropriate length for the tool's simplicity.

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

Completeness3/5

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

While the input side is fully covered (no params), there is no output schema provided. The description omits what the tool returns (recording names? IDs? metadata?), which is critical information for an agent intending to use 'replay_recording' with these results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool accepts zero parameters and schema coverage is 100% (of empty schema). Per scoring rules, 0 parameters warrants baseline score of 4. No additional parameter semantics are needed or provided.

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?

States specific verb 'List' and resource 'saved action recordings/macros' clearly. The term 'macros' helps clarify the domain, but it doesn't explicitly distinguish this viewing operation from sibling execution tools like 'replay_recording' or capture tools like 'start_recording'.

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?

Provides no guidance on when to use this tool versus alternatives. Given siblings like 'replay_recording', 'start_recording', and 'stop_recording', the description should clarify this is for retrieval/inspection rather than execution or capture.

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/divineDev-dotcom/android_mcp'

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