Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_remove_lead_from_list

Remove leads from a Marketo static list by specifying list ID and up to 300 lead IDs.

Instructions

Remove one or more leads from a static list. Accepts an array of lead IDs. Max 300 leads per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYes
leadIdsYes

Implementation Reference

  • src/index.ts:402-414 (registration)
    Registration of the 'marketo_remove_lead_from_list' tool using server.tool(). Defines tool name, description, input schema (listId: number, leadIds: array of numbers), and the handler.
    server.tool(
      'marketo_remove_lead_from_list',
      'Remove one or more leads from a static list. Accepts an array of lead IDs. Max 300 leads per call.',
      {
        listId: z.number(),
        leadIds: z.array(z.number()),
      },
      tool(async ({ listId, leadIds }) =>
        makeApiRequest(`/rest/v1/lists/${listId}/leads/delete.json`, 'POST', {
          input: leadIds.map(id => ({ id })),
        })
      )
    );
  • Handler function for removing leads from a list. Wraps makeApiRequest to POST to /rest/v1/lists/{listId}/leads/delete.json with lead IDs mapped as input array.
    tool(async ({ listId, leadIds }) =>
      makeApiRequest(`/rest/v1/lists/${listId}/leads/delete.json`, 'POST', {
        input: leadIds.map(id => ({ id })),
      })
    )
  • Zod schema defining input parameters: listId (z.number()) and leadIds (z.array(z.number())).
    {
      listId: z.number(),
      leadIds: z.array(z.number()),
    },
  • makeApiRequest helper function that handles authentication headers, HTTP method, and API calls to Marketo.
    async function makeApiRequest(
      endpoint: string,
      method: string,
      data?: any,
      contentType: string = 'application/json'
    ) {
      const token = await tokenManager.getToken();
      const headers: Record<string, string> = {
        Authorization: `Bearer ${token}`,
      };
    
      if (contentType) {
        headers['Content-Type'] = contentType;
      }
    
      try {
        const response = await axios({
          url: `${MARKETO_BASE_URL}${endpoint}`,
          method,
          data:
            contentType === 'application/x-www-form-urlencoded'
              ? new URLSearchParams(data).toString()
              : data,
          headers,
        });
        return response.data;
      } catch (error: any) {
        console.error('API request failed:', error.response?.data || error.message);
        throw error;
      }
    }
  • tool wrapper helper that invokes the handler, formats success/error responses for the MCP protocol.
    function tool<T>(handler: (args: T) => Promise<unknown>) {
      return async (args: T) => {
        try {
          const response = await handler(args);
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(response, null, 2) }],
          };
        } catch (error: any) {
          return {
            content: [
              {
                type: 'text' as const,
                text: `Error: ${error.response?.data?.message || error.message}`,
              },
            ],
            isError: true,
          };
        }
      };
    }
Behavior3/5

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

No annotations provided, so description carries full burden. States it removes leads (destructive action) and limits batch size, but lacks details on permissions, reversibility, or error handling.

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 concise sentences, front-loaded with purpose followed by a constraint. No unnecessary words or redundant information.

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

Completeness4/5

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

Given simple parameters and no output schema, description adequately covers operation and batch limit. Lacks details on edge cases (e.g., leads not in list, multiple lists) but sufficient for a straightforward removal tool.

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 has 2 params with 0% description coverage. Description clarifies leadIds as 'array of lead IDs' but does not explain listId, though its name is self-explanatory. Adds some value but incomplete.

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?

The description clearly states 'Remove one or more leads from a static list', specifying the verb (remove), resource (leads from a static list), and implicitly distinguishing it from the sibling tool 'marketo_add_lead_to_list'.

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?

Provides a key constraint (Max 300 leads per call) and clear usage context, but does not explicitly mention when not to use this tool or direct to alternatives like marketo_add_lead_to_list.

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

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