Skip to main content
Glama
VetCoders

automator-mcp

by VetCoders

create_workflow

Create new Automator workflows to automate macOS tasks like file organization, email sending, and system operations using AppleScript or JXA actions.

Instructions

Create a new Automator workflow file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the workflow
typeYesType of Automator document
actionsNoArray of action configurations

Implementation Reference

  • The handler function that implements the 'create_workflow' tool logic. It generates an AppleScript to create a new Automator workflow with the given name and type, executes it, and returns a success message.
    async createWorkflow(args) {
      // Simplified workflow creation - in real implementation would use Automator's plist format
      const workflowScript = `
        tell application "Automator"
          make new workflow
          set name of result to "${args.name}"
          save result
        end tell
      `;
      
      await this.runAppleScript(workflowScript);
      
      return {
        content: [
          {
            type: 'text',
            text: `Created ${args.type} workflow: ${args.name}`,
          },
        ],
      };
    }
  • src/index.js:65-94 (registration)
    Registration of the 'create_workflow' tool in the listTools response, including name, description, and input schema definition.
    {
      name: 'create_workflow',
      description: 'Create a new Automator workflow file',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the workflow',
          },
          type: {
            type: 'string',
            enum: ['workflow', 'application', 'service', 'quick-action'],
            description: 'Type of Automator document',
          },
          actions: {
            type: 'array',
            description: 'Array of action configurations',
            items: {
              type: 'object',
              properties: {
                action: { type: 'string' },
                parameters: { type: 'object' },
              },
            },
          },
        },
        required: ['name', 'type'],
      },
    },
  • Dispatch handler case that routes 'create_workflow' tool calls to the createWorkflow method.
    case 'create_workflow':
      return await this.createWorkflow(args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation tool but doesn't mention permissions required, whether it overwrites existing files, what format the workflow file takes, or any side effects. For a creation tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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, efficient sentence that states the core purpose without any fluff. It's appropriately sized and front-loaded, 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?

For a creation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after creation, what format the workflow file takes, whether it's saved somewhere specific, or what permissions might be required. Given the complexity of workflow creation and the lack of structured metadata, more context is needed.

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?

The schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description doesn't add any meaning beyond what's in the schema - it doesn't explain relationships between parameters, provide examples, or clarify usage patterns. This meets the baseline for high schema coverage.

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?

The description clearly states the action ('Create') and resource ('new Automator workflow file'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'quick_action' or 'system_automation' which might also create workflow-related artifacts, so it doesn't reach the highest score.

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 like 'quick_action' or 'run_applescript'. It doesn't mention prerequisites, dependencies, or typical use cases, leaving the agent with minimal context for selection.

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