Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_get_email_by_id

Retrieve a single email by numeric ID. Returns full metadata including subject, from address, reply-to, and folder location.

Instructions

Retrieve a single email by its numeric ID. Returns full email metadata including subject, from address, reply-to, template, and folder location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailIdYes

Implementation Reference

  • src/index.ts:518-523 (registration)
    Registration of the 'marketo_get_email_by_id' tool with its name, description, schema, and handler on the MCP server.
    server.tool(
      'marketo_get_email_by_id',
      'Retrieve a single email by its numeric ID. Returns full email metadata including subject, from address, reply-to, template, and folder location.',
      { emailId: z.number() },
      tool(async ({ emailId }) => makeApiRequest(`/asset/v1/email/${emailId}.json`, 'GET'))
    );
  • Input schema requiring a single 'emailId' parameter of type z.number(), validated via Zod.
    { emailId: z.number() },
  • Handler function for the tool: makes a GET request to /asset/v1/email/{emailId}.json using the makeApiRequest helper.
    tool(async ({ emailId }) => makeApiRequest(`/asset/v1/email/${emailId}.json`, 'GET'))
  • The makeApiRequest helper function that constructs and executes HTTP requests with authentication headers, used by the tool handler.
    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 helper that wraps handler functions to format successful responses as JSON text and errors with proper isError flag.
    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 provided, so description carries the burden. It states it returns metadata, implying a read-only operation, but does not explicitly confirm safety, permissions, or rate limits. Adequate but lacks explicit behavioral disclosure.

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?

Very concise single sentence that front-loads the action. However, could be slightly more structured by separating purpose and return fields.

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 no output schema, description lists key return fields (subject, from address, etc.), providing enough context for a simple retrieval. Lacks error handling or response format details, but acceptable for a straightforward tool.

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

Parameters2/5

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

Schema coverage is 0% for the parameter 'emailId'; the description adds only 'numeric ID', which is already evident from the type. Does not explain where to obtain the ID or any constraints beyond numeric type.

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 identifies the action (retrieve), the resource (a single email by numeric ID), and distinguishes from siblings like 'marketo_get_emails' by specifying it returns full metadata for one email.

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?

Implies usage when you have a numeric ID, but does not explicitly state when to use this vs. alternatives like 'marketo_get_emails' for listing or 'marketo_send_sample_email' for sending. No exclusion criteria.

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