Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_get_lead_lists

Retrieve all static lists associated with a lead using Marketo API. Supports cursor-based pagination to handle large results.

Instructions

Get all static lists that a lead belongs to. Supports cursor-based pagination via nextPageToken. Returns list IDs and names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadIdYes
batchSizeNo
nextPageTokenNo

Implementation Reference

  • src/index.ts:370-386 (registration)
    Registration of the 'marketo_get_lead_lists' tool on the MCP server with name, description, and Zod schema.
    server.tool(
      'marketo_get_lead_lists',
      'Get all static lists that a lead belongs to. Supports cursor-based pagination via nextPageToken. Returns list IDs and names.',
      {
        leadId: z.number(),
        batchSize: z.number().optional(),
        nextPageToken: z.string().optional(),
      },
      tool(async ({ leadId, batchSize = 100, nextPageToken }) => {
        const params = new URLSearchParams({ batchSize: batchSize.toString() });
        if (nextPageToken) params.append('nextPageToken', nextPageToken);
        return makeApiRequest(
          `/rest/v1/lists/${leadId}/leads.json?${params.toString()}`,
          'GET'
        );
      })
    );
  • Zod schema defining input parameters: leadId (number, required), batchSize (optional number), nextPageToken (optional string).
    {
      leadId: z.number(),
      batchSize: z.number().optional(),
      nextPageToken: z.string().optional(),
    },
  • Handler function for 'marketo_get_lead_lists' - constructs URL with leadId, batchSize, and optional nextPageToken parameters, then calls makeApiRequest with GET method.
    tool(async ({ leadId, batchSize = 100, nextPageToken }) => {
      const params = new URLSearchParams({ batchSize: batchSize.toString() });
      if (nextPageToken) params.append('nextPageToken', nextPageToken);
      return makeApiRequest(
        `/rest/v1/lists/${leadId}/leads.json?${params.toString()}`,
        'GET'
      );
    })
  • Helper function called by the handler - makeApiRequest performs the actual HTTP GET request to the Marketo API with authentication headers.
    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;
      }
    }
  • Helper 'tool' wrapper function that wraps the handler with try/catch and formats the response as MCP content with JSON stringification.
    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?

No annotations are provided, so the description carries full burden. It mentions pagination and return fields but does not disclose side effects (likely read-only), error handling, or rate limits. Adequate but not comprehensive.

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?

Two concise sentences: first defines purpose, second adds pagination and output. No redundant words or extraneous information.

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 simple tool (3 params, no output schema), description adequately covers purpose, pagination, and return shape. Could mention that lists are static only, but overall sufficient.

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

Parameters4/5

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

With 0% schema description coverage, the description adds meaning: 'Supports cursor-based pagination via nextPageToken' explains pagination, and 'Returns list IDs and names' hints at output. leadId is obvious, but batchSize is not explained.

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 'Get all static lists that a lead belongs to', specifying the verb and resource. It distinguishes from siblings like marketo_get_lead_by_id or marketo_add_lead_to_list by focusing on list membership.

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

Usage Guidelines4/5

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

The description implies usage for retrieving lists for a lead. It mentions pagination but does not explicitly state when not to use or compare to alternatives like marketo_get_lead_activities.

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