Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_get_smart_lists

Retrieve smart lists from Marketo with pagination. Returns metadata like filter rules and folder location.

Instructions

List smart lists in the Marketo instance. Paginate with maxReturn (default 200) and offset. Returns smart list metadata including filter rules and folder location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxReturnNo
offsetNo

Implementation Reference

  • src/index.ts:149-163 (registration)
    Registration of 'marketo_get_smart_lists' tool via server.tool(), which also contains the schema inline and the handler logic as an anonymous async function.
    server.tool(
      'marketo_get_smart_lists',
      'List smart lists in the Marketo instance. Paginate with maxReturn (default 200) and offset. Returns smart list metadata including filter rules and folder location.',
      {
        maxReturn: z.number().optional(),
        offset: z.number().optional(),
      },
      tool(async ({ maxReturn = 200, offset = 0 }) => {
        const params = new URLSearchParams({
          maxReturn: maxReturn.toString(),
          offset: offset.toString(),
        });
        return makeApiRequest(`/asset/v1/smartLists.json?${params.toString()}`, 'GET');
      })
    );
  • Handler function for marketo_get_smart_lists. Accepts maxReturn and offset, builds query params, and calls GET /asset/v1/smartLists.json.
    tool(async ({ maxReturn = 200, offset = 0 }) => {
      const params = new URLSearchParams({
        maxReturn: maxReturn.toString(),
        offset: offset.toString(),
      });
      return makeApiRequest(`/asset/v1/smartLists.json?${params.toString()}`, 'GET');
    })
  • Zod schema defining input parameters: maxReturn (optional number) and offset (optional number).
    {
      maxReturn: z.number().optional(),
      offset: z.number().optional(),
    },
  • Helper function makeApiRequest used by the handler to execute HTTP requests against the Marketo API.
    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 wrapper 'tool()' that wraps handler functions with try/catch, returning standardized content responses.
    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,
          };
        }
      };
    }
Behavior4/5

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

With no annotations, the description provides key behavioral details: it is a read operation, paginates via maxReturn and offset, and returns smart list metadata including filter rules and folder location. No contradictions.

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?

The description is two sentences, no extraneous words, and front-loads the essential function.

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?

For a simple list operation with two optional parameters and no output schema, the description covers the action, pagination, and return contents; lacks only offset default value.

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?

Schema coverage is 0%, but the description explains the purpose of maxReturn (with default 200) and offset for pagination, adding meaning beyond the bare schema.

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 action 'List' and the resource 'smart lists in the Marketo instance', distinguishing it from siblings like marketo_get_smart_list_by_id which fetches a single smart list.

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 listing all smart lists with pagination, but does not explicitly contrast with sibling tools or explain when not to use this tool.

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