Skip to main content
Glama

marketo_enqueue_bulk_export

Enqueue a previously created bulk export job to change its status from Created to Queued, initiating processing. Use with marketo_get_bulk_export_status to monitor progress.

Instructions

Enqueue a previously created bulk export job for processing. The job moves from Created to Queued status. Poll status with marketo_get_bulk_export_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exportIdYesExport job ID returned from create

Implementation Reference

  • The tool handler for 'marketo_enqueue_bulk_export'. Takes an exportId string, sends a POST request to `/bulk/v1/leads/export/{exportId}/enqueue.json` to enqueue the bulk export job.
    server.tool(
      "marketo_enqueue_bulk_export",
      "Enqueue a previously created bulk export job for processing. The job moves from Created to Queued status. Poll status with marketo_get_bulk_export_status.",
      {
        exportId: z.string().describe("Export job ID returned from create"),
      },
      async (args) => {
        try {
          return ok(await makeRequest(
            `/bulk/v1/leads/export/${args.exportId}/enqueue.json`,
            "POST"
          ));
        } catch (e) { return err(e); }
      }
    );
  • Input schema for the tool: requires a string 'exportId' described as the export job ID returned from create.
    {
      exportId: z.string().describe("Export job ID returned from create"),
    },
  • src/index.ts:13-13 (registration)
    Import of the registerBulkExportTools function from the bulkExport module.
    import { registerBulkExportTools } from "./tools/bulkExport.js";
  • src/index.ts:29-29 (registration)
    Registration call: registerBulkExportTools(server) which registers the tool on the MCP server.
    registerBulkExportTools(server);
  • The makeRequest helper used by the handler to send authenticated HTTP requests to the Marketo API.
    export async function makeRequest<T = unknown>(
      endpoint: string,
      method: Method = "GET",
      data?: unknown,
      contentType?: string,
    ): Promise<T> {
      const token = await getAccessToken();
      const config: AxiosRequestConfig = {
        url: `${MARKETO_BASE_URL}${endpoint}`,
        method,
        headers: {
          Authorization: `Bearer ${token}`,
          ...(contentType ? { "Content-Type": contentType } : {}),
        },
        ...(data && method !== "GET" ? { data } : {}),
        ...(data && method === "GET" ? { params: data } : {}),
      };
    
      const res = await axios(config);
      const body = res.data;
    
      // Marketo REST API returns errors inside the response body
      if (body?.errors?.length) {
        const e = body.errors[0];
        throw new MarketoError(`${e.code}: ${e.message}`, res.status);
      }
    
      return body as T;
    }
Behavior3/5

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

No annotations provided. Description discloses the state change but does not mention side effects, permissions, or error conditions. Adequate but minimal behavioral context.

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?

Two sentences, front-loaded with action. Every sentence adds value without redundancy.

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

Completeness5/5

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

For a tool with a single parameter and no output schema, the description is sufficient. It covers action, input, state transition, and follow-up action.

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 description for exportId. The description adds no additional parameter semantics beyond what the schema provides.

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?

Description clearly states the action (enqueue), the resource (bulk export job), and the state transition (Created to Queued). It distinguishes from sibling tools like marketo_create_bulk_export_leads and marketo_get_bulk_export_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies prerequisite (job must be created first) and suggests polling status with another tool. However, it does not explicitly state when not to use or alternative tools for other states.

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/ZLeventer/marketo-mcp-server'

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