Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_get_channels

Retrieve all program channels in your Marketo instance to see available progression statuses for program types, such as Webinar with Invited, Registered, and Attended.

Instructions

List all program channels in the instance. Channels define the progression statuses available to programs (e.g., Webinar: Invited > Registered > Attended).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxReturnNo
offsetNo

Implementation Reference

  • The handler function that executes the 'marketo_get_channels' tool logic. It takes optional maxReturn and offset parameters, constructs a query string, and calls the Marketo Asset API GET /asset/v1/channels.json endpoint.
    tool(async ({ maxReturn = 200, offset = 0 }) => {
      const params = new URLSearchParams({
        maxReturn: maxReturn.toString(),
        offset: offset.toString(),
      });
      return makeApiRequest(`/asset/v1/channels.json?${params.toString()}`, 'GET');
    })
  • Input schema for the tool: optional 'maxReturn' (number) and 'offset' (number) parameters, defined using Zod.
    {
      maxReturn: z.number().optional(),
      offset: z.number().optional(),
    },
  • src/index.ts:178-192 (registration)
    Registration of the 'marketo_get_channels' tool with the MCP server using server.tool(), including name, description, schema, and handler.
    server.tool(
      'marketo_get_channels',
      'List all program channels in the instance. Channels define the progression statuses available to programs (e.g., Webinar: Invited > Registered > Attended).',
      {
        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/channels.json?${params.toString()}`, 'GET');
      })
    );
  • The makeApiRequest helper function that handles authentication token injection, HTTP request execution via Axios, and error handling for all API calls including this tool.
    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 handlers with error handling and formats responses into MCP content blocks.
    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?

No annotations provided. Description indicates a read operation but does not mention pagination or performance implications despite input schema having maxReturn and offset.

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?

Two concise sentences with no fluff, though could benefit from brief parameter notes.

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?

Missing output schema and parameter details; for a simple list tool it's acceptable but incomplete for an agent to use confidently.

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?

Input schema has 0% parameter description coverage and the description does not explain maxReturn or offset parameters, leaving the agent to infer their meaning.

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?

Explicitly states 'List all program channels in the instance' and explains what channels are, clearly differentiating from create/delete/update siblings.

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?

Implied usage for listing channels, but no guidance on when to use this vs get_channel_by_id or other list tools.

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