Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_delete_lead

Permanently remove a lead record from Marketo using its lead ID. This action is irreversible.

Instructions

Permanently delete a lead by its numeric ID. This action cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadIdYes

Implementation Reference

  • src/index.ts:315-320 (registration)
    Registration of the 'marketo_delete_lead' tool with the MCP server, including description and Zod schema for leadId.
    server.tool(
      'marketo_delete_lead',
      'Permanently delete a lead by its numeric ID. This action cannot be undone.',
      { leadId: z.number() },
      tool(async ({ leadId }) => makeApiRequest(`/rest/v1/leads/${leadId}/delete.json`, 'POST'))
    );
  • Input schema for 'marketo_delete_lead': leadId is a required number (z.number()).
    { leadId: z.number() },
  • Handler for 'marketo_delete_lead': calls makeApiRequest to POST to /rest/v1/leads/{leadId}/delete.json. The 'tool' wrapper (lines 55-74) provides error handling and response formatting.
    tool(async ({ leadId }) => makeApiRequest(`/rest/v1/leads/${leadId}/delete.json`, 'POST'))
  • The makeApiRequest helper function used by the tool handler to make authenticated HTTP requests to the Marketo API.
    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;
      }
    }
  • The 'tool' wrapper function that wraps handler logic, captures errors, and formats the response as MCP content.
    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?

Without annotations, the description must carry the burden of behavioral disclosure. It correctly flags the destructive nature ('permanently delete', 'cannot be undone'), but lacks additional transparency about permissions, side effects, or response behavior.

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 extremely concise—two sentences with no extraneous words. Every sentence serves a purpose: stating the action and emphasizing irreversibility.

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 the simplicity of the tool (one parameter, no output schema), the description provides adequate context: what it does, how to identify the lead, and the permanence. Minor gaps exist (e.g., no explanation of the response), but overall it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% parameter description coverage, and the description merely reiterates that the ID is numeric. It adds minimal value beyond the schema's type constraint, failing to explain the format or valid range of the leadId.

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 the action (delete), the resource (lead), and the method (by numeric ID). It distinguishes the tool from siblings like marketo_get_lead_by_id and marketo_create_or_update_lead, which perform different operations.

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 explicit guidance on when to use this tool versus alternatives. While it warns about permanence ('cannot be undone'), it does not offer context about prerequisites, typical use cases, or when not to use it.

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