Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_get_lead_by_email

Retrieve a lead record from Marketo by email address. Optionally specify fields to return. Uses the Marketo leads filter API.

Instructions

Look up a lead by email address using the Marketo leads filter API. Optionally specify which fields to return. Returns matching lead records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYes
fieldsNo

Implementation Reference

  • src/index.ts:269-284 (registration)
    Registration of the 'marketo_get_lead_by_email' tool via server.tool() on the McpServer instance. Defines name, description, input schema, and handler.
    server.tool(
      'marketo_get_lead_by_email',
      'Look up a lead by email address using the Marketo leads filter API. Optionally specify which fields to return. Returns matching lead records.',
      {
        email: z.string().email(),
        fields: z.array(z.string()).optional(),
      },
      tool(async ({ email, fields }) => {
        const params = new URLSearchParams({
          filterType: 'email',
          filterValues: email,
        });
        if (fields) params.append('fields', fields.join(','));
        return makeApiRequest(`/rest/v1/leads.json?${params.toString()}`, 'GET');
      })
    );
  • Input schema for 'marketo_get_lead_by_email' using zod: requires 'email' (validated .email()) and optional 'fields' (array of strings).
    {
      email: z.string().email(),
      fields: z.array(z.string()).optional(),
    },
  • Handler function for 'marketo_get_lead_by_email'. Builds query params with filterType=email and filterValues=<email>, optionally appends fields, then calls makeApiRequest to GET /rest/v1/leads.json.
    tool(async ({ email, fields }) => {
      const params = new URLSearchParams({
        filterType: 'email',
        filterValues: email,
      });
      if (fields) params.append('fields', fields.join(','));
      return makeApiRequest(`/rest/v1/leads.json?${params.toString()}`, 'GET');
    })
  • The makeApiRequest helper function that executes the actual HTTP request to the Marketo API with bearer token authentication.
    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 the handler to format successful responses as text content and handle errors consistently.
    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,
          };
        }
      };
    }
Behavior2/5

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

With no annotations, the description should fully disclose behavioral traits. It mentions 'using the Marketo leads filter API' but does not address rate limits, authentication, error handling for missing emails, or duplicate handling. This is insufficient.

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

Conciseness4/5

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

The description is two sentences, concise and front-loaded. However, it could be slightly more efficient by merging the second and third sentences.

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

Completeness2/5

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

No output schema exists, and the description omits return format, error scenarios, and pagination. For a lookup tool with sibling mutation tools, this is incomplete.

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?

Schema coverage is 0%, so the description must compensate. It only states 'Optionally specify which fields to return,' adding minimal value. No explanation of valid fields or format is provided.

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 tool's function: 'Look up a lead by email address' using the Marketo API, with optional field selection and returning matching records. This distinguishes it from siblings like get_lead_by_id.

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

Usage Guidelines3/5

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

The description implies usage for retrieving a lead by email but offers no explicit guidance on when to use this tool versus alternatives like get_lead_by_id or create_or_update_lead.

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