Skip to main content
Glama

marketo_get_lead_changes

Retrieve changes to specific lead data in Marketo by providing a lead ID, with options to filter fields, set batch size, and paginate results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadIdYes
fieldsNo
nextPageTokenNo
batchSizeNo

Implementation Reference

  • The main handler function for the 'marketo_get_lead_changes' tool. It constructs query parameters for fields and pagination, calls the Marketo REST API endpoint `/rest/v1/activities/lead/{leadId}/changes.json`, and returns the response or error.
    async ({ leadId, fields, nextPageToken, batchSize = 100 }) => { try { const params = new URLSearchParams({ batchSize: batchSize.toString(), }); if (fields) { params.append('fields', fields.join(',')); } if (nextPageToken) { params.append('nextPageToken', nextPageToken); } const response = await makeApiRequest( `/rest/v1/activities/lead/${leadId}/changes.json?${params.toString()}`, 'GET' ); 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 validation for the tool parameters: required leadId, optional fields array, nextPageToken, and batchSize.
    { leadId: z.number(), fields: z.array(z.string()).optional(), nextPageToken: z.string().optional(), batchSize: z.number().optional(), },
  • src/index.ts:562-599 (registration)
    Full registration of the 'marketo_get_lead_changes' tool using server.tool(), including the tool name, input schema, and inline handler function.
    server.tool( 'marketo_get_lead_changes', { leadId: z.number(), fields: z.array(z.string()).optional(), nextPageToken: z.string().optional(), batchSize: z.number().optional(), }, async ({ leadId, fields, nextPageToken, batchSize = 100 }) => { try { const params = new URLSearchParams({ batchSize: batchSize.toString(), }); if (fields) { params.append('fields', fields.join(',')); } if (nextPageToken) { params.append('nextPageToken', nextPageToken); } const response = await makeApiRequest( `/rest/v1/activities/lead/${leadId}/changes.json?${params.toString()}`, 'GET' ); 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}` }, ], }; } } );
  • Shared utility function used by the handler to make authenticated HTTP requests to the Marketo API, handling token retrieval and error logging.
    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; } }

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