Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_get_program_by_id

Retrieve full program metadata including channel, status, costs, tags, and folder path by providing the program's numeric ID.

Instructions

Retrieve a single program by its numeric ID. Returns full program metadata including channel, status, costs, tags, and folder path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
programIdYes

Implementation Reference

  • src/index.ts:445-450 (registration)
    Registers the 'marketo_get_program_by_id' MCP tool with a programId parameter. The handler is an inline function that makes a GET request to the Marketo API endpoint /asset/v1/program/{programId}.json.
    server.tool(
      'marketo_get_program_by_id',
      'Retrieve a single program by its numeric ID. Returns full program metadata including channel, status, costs, tags, and folder path.',
      { programId: z.number() },
      tool(async ({ programId }) => makeApiRequest(`/asset/v1/program/${programId}.json`, 'GET'))
    );
  • Defines the input schema: a single required numeric parameter 'programId' validated via Zod.
    { programId: z.number() },
  • The handler logic wrapped by the 'tool' helper function. It calls makeApiRequest with the program endpoint using the provided programId.
    tool(async ({ programId }) => makeApiRequest(`/asset/v1/program/${programId}.json`, 'GET'))
  • The 'tool' helper that wraps handler functions, converting their return value into MCP text content or an error response.
    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,
          };
        }
      };
  • The makeApiRequest helper that authenticates via TokenManager and performs the HTTP request to 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;
      }
    }
Behavior3/5

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

No annotations exist, so the description carries full burden. While it indicates a read operation (retrieve), it does not explicitly state no side effects, required permissions, or behavior on invalid IDs. The description is adequate but lacks explicit non-mutation confirmation.

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 a single concise sentence, front-loading the core action and resource, then listing return elements. No superfluous words, making it efficient and easy to parse.

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 the low complexity (1 required param, no output schema), the description covers the main purpose, return content, and ID type. It could briefly mention error handling or permissions, but overall it is sufficiently complete for a simple retrieval tool.

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

Parameters3/5

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

The schema has one parameter (programId) with 0% description coverage. The description mentions 'by its numeric ID', adding minimal context that the ID is numeric, but does not fully describe the parameter’s purpose, constraints, or how to obtain it. More detail would be beneficial.

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 specifies the action (Retrieve), resource (single program), key identifier (numeric ID), and expected return content (full metadata with channel, status, costs, tags, folder path). This differentiates it from sibling tools like get_programs or get_program_members.

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 when a specific program is needed, but it omits explicit guidance on when to use this tool versus alternatives, such as get_programs for listing all programs or get_program_members for members. No prerequisites, exclusions, or comparison to siblings are provided.

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