Skip to main content
Glama
VetCoders

automator-mcp

by VetCoders

list_actions

Discover available automation actions for macOS, including AppleScript execution, workflow automation, and system tasks like email management and file organization.

Instructions

List available Automator actions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category (optional)

Implementation Reference

  • The primary handler function for the 'list_actions' tool. It executes an AppleScript to fetch names of Automator actions, parses the result, and returns a formatted text response.
    async listActions(category) {
      const script = `
        tell application "Automator"
          get name of Automator actions
        end tell
      `;
      
      const result = await this.runAppleScript(script);
      const actions = result.content[0].text.split(', ');
      
      return {
        content: [
          {
            type: 'text',
            text: `Available actions${category ? ` in ${category}` : ''}:\n${actions.join('\n')}`,
          },
        ],
      };
    }
  • src/index.js:95-107 (registration)
    Registration of the 'list_actions' tool in the ListTools response, including its name, description, and input schema.
    {
      name: 'list_actions',
      description: 'List available Automator actions',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Filter by category (optional)',
          },
        },
      },
    },
  • Dispatch case in the CallToolRequestSchema handler that routes 'list_actions' calls to the listActions method.
    case 'list_actions':
      return await this.listActions(args.category);
  • Input schema definition for the 'list_actions' tool, specifying an optional 'category' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        category: {
          type: 'string',
          description: 'Filter by category (optional)',
        },
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('List available Automator actions') without revealing behavioral traits such as whether it's read-only, if it requires permissions, how results are formatted (e.g., pagination, sorting), or any rate limits. This leaves significant gaps for an agent to understand how to interact with it effectively.

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 sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple tool. Every word earns its place, making it easy for an agent to parse quickly.

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 tool's simplicity (1 optional parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what 'available' means (e.g., system-wide, user-specific, or based on permissions), the format of the returned list, or how it relates to sibling tools. For a discovery tool in an automation context, more context is needed to guide effective use.

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 input schema has 1 parameter with 100% description coverage, documenting it as an optional filter by category. The description doesn't add any parameter semantics beyond what the schema provides, but since there's only one optional parameter and the schema is fully documented, the baseline is high. A score of 4 reflects that the description doesn't need to compensate for schema gaps in this minimal case.

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

Purpose3/5

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

The description states the tool's purpose ('List available Automator actions') which is clear but vague. It specifies the verb ('List') and resource ('Automator actions'), but doesn't distinguish it from potential sibling tools like 'quick_action' or 'system_automation' that might also involve actions. The description is adequate but lacks specificity about what 'available' means in this context.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'create_workflow' or 'run_applescript', nor does it explain if this is for discovery, configuration, or other purposes. Without context, an agent must infer usage from the tool name alone, which is insufficient.

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/VetCoders/automator-mcp'

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