Skip to main content
Glama
elgentos

Magento 2 Development MCP Server

by elgentos

Cron List

sys-cron-list

View all Magento 2 cron jobs and their configuration settings to monitor scheduled tasks and optimize system performance.

Instructions

List all Magento 2 cron jobs and their configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput formattable

Implementation Reference

  • The handler function that executes the 'magerun2 sys:cron:list' command with the specified format, processes the result (including JSON parsing if needed), handles errors, and returns formatted content for MCP.
    async ({ format = "table" }) => {
      const command = `magerun2 sys:cron:list --format=${format}`;
      const result = await executeMagerun2Command(command, format === "json");
    
      if (!result.success) {
        return {
          content: [{
            type: "text",
            text: result.error
          }],
          isError: true
        };
      }
    
      const responseText = format === "json"
        ? `Cron job list (${format} format):\n\n${JSON.stringify(result.data, null, 2)}`
        : `Cron job list (${format} format):\n\n${result.data}`;
    
      return {
        content: [{
          type: "text",
          text: responseText
        }]
      };
    }
  • The Zod input schema defining the optional 'format' parameter for output format (table, json, csv) with default 'table'.
    inputSchema: {
      format: z.enum(["table", "json", "csv"])
        .default("table")
        .describe("Output format")
    }
  • src/index.ts:1290-1327 (registration)
    The server.registerTool call that registers the 'sys-cron-list' tool, specifying its title, description, input schema, and handler function.
    server.registerTool(
      "sys-cron-list",
      {
        title: "Cron List",
        description: "List all Magento 2 cron jobs and their configuration",
        inputSchema: {
          format: z.enum(["table", "json", "csv"])
            .default("table")
            .describe("Output format")
        }
      },
      async ({ format = "table" }) => {
        const command = `magerun2 sys:cron:list --format=${format}`;
        const result = await executeMagerun2Command(command, format === "json");
    
        if (!result.success) {
          return {
            content: [{
              type: "text",
              text: result.error
            }],
            isError: true
          };
        }
    
        const responseText = format === "json"
          ? `Cron job list (${format} format):\n\n${JSON.stringify(result.data, null, 2)}`
          : `Cron job list (${format} format):\n\n${result.data}`;
    
        return {
          content: [{
            type: "text",
            text: responseText
          }]
        };
      }
    );
  • Shared helper utility function used by the handler (and other tools) to execute magerun2 commands safely with consistent error handling, timeouts, and optional JSON parsing.
    async function executeMagerun2Command(command: string, parseJson: boolean = false): Promise<{
      success: true;
      data: any;
      rawOutput: string;
    } | {
      success: false;
      error: string;
      isError: true;
    }> {
      try {
        const { stdout, stderr } = await execAsync(command, {
          cwd: process.cwd(),
          timeout: 30000 // 30 second timeout
        });
    
        if (stderr && stderr.trim()) {
          console.error("magerun2 stderr:", stderr);
        }
    
        if (parseJson) {
          try {
            return { success: true, data: JSON.parse(stdout), rawOutput: stdout };
          } catch (parseError) {
            return {
              success: false,
              error: `Error parsing magerun2 JSON output: ${parseError}\n\nRaw output:\n${stdout}`,
              isError: true
            };
          }
        }
    
        return { success: true, data: stdout.trim(), rawOutput: stdout };
    
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
    
        // Check if magerun2 is not found
        if (errorMessage.includes("command not found") || errorMessage.includes("not recognized")) {
          return {
            success: false,
            error: "Error: magerun2 command not found. Please ensure n98-magerun2 is installed and available in your PATH.\n\nInstallation instructions: https://github.com/netz98/n98-magerun2",
            isError: true
          };
        }
    
        // Check if not in Magento directory
        if (errorMessage.includes("not a Magento installation") || errorMessage.includes("app/etc/env.php")) {
          return {
            success: false,
            error: "Error: Current directory does not appear to be a Magento 2 installation. Please run this command from your Magento 2 root directory.",
            isError: true
          };
        }
    
        return {
          success: false,
          error: `Error executing magerun2 command: ${errorMessage}`,
          isError: true
        };
      }
    }
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. While it implies a read-only operation ('List'), it doesn't specify whether this requires specific permissions, how data is retrieved (e.g., from database or configuration files), potential performance impacts, or error handling. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 front-loads the core purpose without unnecessary details. Every word earns its place, making it easy to parse quickly. No redundancy or verbose explanations detract from clarity.

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?

Given the tool's low complexity (one optional parameter, no output schema), the description is minimally adequate but lacks depth. It doesn't explain what 'configuration' includes (e.g., schedule, status, last run), how results are structured, or potential limitations (e.g., pagination). With no annotations and simple schema, more context would improve completeness for effective use.

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 input schema has 100% description coverage, with the single parameter 'format' well-documented (including enum values and default). The description adds no additional parameter semantics beyond what the schema provides, such as explaining the implications of each format choice (e.g., 'table' for human-readable output vs. 'json' for programmatic use). Baseline 3 is appropriate since the schema does the heavy lifting.

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 verb ('List') and resource ('all Magento 2 cron jobs and their configuration'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'sys-cron-run' (which executes cron jobs) or 'sys-check' (which might check cron status), leaving some ambiguity about when to choose this specific list tool over alternatives.

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. With siblings like 'sys-cron-run' (for executing cron jobs) and 'sys-check' (potentially for cron-related diagnostics), there's no indication of context, prerequisites, or exclusions. This lack of comparative guidance could lead to misuse or confusion in tool 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/elgentos/magento2-dev-mcp'

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