Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_get_lead_by_id

Retrieve specific lead details from Marketo by providing the lead ID and optional fields to fetch targeted information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadIdYes
fieldsNo

Implementation Reference

  • src/index.ts:383-412 (registration)
    Registration of the 'marketo_get_lead_by_id' tool using McpServer.tool(). Includes inline Zod schema for parameters (leadId required number, fields optional string array) and the complete inline async handler function. The handler builds the Marketo REST API endpoint /rest/v1/lead/{leadId}.json with optional 'fields' query parameter, calls the makeApiRequest helper to fetch data, formats the response as JSON text content, or returns an error message on failure.
    server.tool(
      'marketo_get_lead_by_id',
      {
        leadId: z.number(),
        fields: z.array(z.string()).optional(),
      },
      async ({ leadId, fields }) => {
        try {
          const params = new URLSearchParams();
          if (fields) {
            params.append('fields', fields.join(','));
          }
    
          const response = await makeApiRequest(
            `/rest/v1/lead/${leadId}.json${params.toString() ? `?${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}` },
            ],
          };
        }
      }
    );
  • Core helper function called by the tool handler to execute authenticated HTTP requests to Marketo API. Retrieves Bearer token via TokenManager, sets headers, uses axios for the request (handling form-urlencoded data), returns response.data, and re-throws errors after 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;
      }
    }
  • TokenManager class provides getToken() method for obtaining and caching OAuth2 access tokens using client credentials flow against Marketo's identity endpoint. Used by makeApiRequest to authenticate all API calls. Instantiated globally with env vars.
    class TokenManager {
      private clientId: string;
      private clientSecret: string;
      private accessToken: string | null = null;
      private tokenExpiry: number = 0;
    
      constructor(clientId: string, clientSecret: string) {
        this.clientId = clientId;
        this.clientSecret = clientSecret;
      }
    
      async getToken(): Promise<string> {
        // Check if we have a valid token
        if (this.accessToken && Date.now() < this.tokenExpiry) {
          return this.accessToken;
        }
    
        try {
          // Extract the identity URL from the base URL
          // Convert from https://instance.mktorest.com/rest to https://instance.mktorest.com/identity
          const identityUrl = MARKETO_BASE_URL.replace('/rest', '/identity');
    
          const response = await axios.get(`${identityUrl}/oauth/token`, {
            params: {
              grant_type: 'client_credentials',
              client_id: this.clientId,
              client_secret: this.clientSecret,
            },
          });
    
          const data = response.data as TokenResponse;
          this.accessToken = data.access_token;
          // Set expiry to slightly before the actual expiry to ensure we don't use an expired token
          this.tokenExpiry = Date.now() + (data.expires_in - 60) * 1000;
    
          return this.accessToken;
        } catch (error: any) {
          console.error('Failed to get Marketo access token:', error.response?.data || error.message);
          throw new Error('Failed to authenticate with Marketo');
        }
      }
    }
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