Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_delete_lead

Remove a lead from Marketo by specifying the lead ID to manage your CRM data and maintain clean records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadIdYes

Implementation Reference

  • src/index.ts:497-517 (registration)
    Registration of the 'marketo_delete_lead' MCP tool, including inline input schema (leadId: z.number()) and handler function that performs a POST request to the Marketo API endpoint `/rest/v1/leads/${leadId}/delete.json` using the shared makeApiRequest helper.
    server.tool(
      'marketo_delete_lead',
      {
        leadId: z.number(),
      },
      async ({ leadId }) => {
        try {
          const response = await makeApiRequest(`/rest/v1/leads/${leadId}/delete.json`, 'POST');
    
          return {
            content: [{ type: 'text', text: JSON.stringify(response, null, 2) }],
          };
        } catch (error: any) {
          return {
            content: [
              { type: 'text', text: `Error: ${error.response?.data?.message || error.message}` },
            ],
          };
        }
      }
    );
  • The core handler logic for executing the marketo_delete_lead tool: authenticates via token, sends POST to delete endpoint, returns JSON response or error message.
    async ({ leadId }) => {
      try {
        const response = await makeApiRequest(`/rest/v1/leads/${leadId}/delete.json`, 'POST');
    
        return {
          content: [{ type: 'text', text: JSON.stringify(response, null, 2) }],
        };
      } catch (error: any) {
        return {
          content: [
            { type: 'text', text: `Error: ${error.response?.data?.message || error.message}` },
          ],
        };
      }
    }
  • Zod input schema defining the required 'leadId' parameter as a number.
    {
      leadId: z.number(),
    },
  • Shared helper function makeApiRequest used by all Marketo tools, including marketo_delete_lead, to handle authenticated API calls with axios, token management, and error handling.
    async function makeApiRequest(
      endpoint: string,
      method: string,
      data?: any,
      contentType: string = 'application/json'
    ) {
      const token = await tokenManager.getToken();
      const headers: any = {
        Authorization: `Bearer ${token}`,
      };
    
      if (contentType) {
        headers['Content-Type'] = contentType;
      }
    
      try {
        const response = await axios({
          url: `${MARKETO_BASE_URL}${endpoint}`,
          method: 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;
      }
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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