Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_get_form_by_id

Retrieve a Marketo form's complete metadata, including fields, submit button, and thank-you page configuration, by its numeric ID.

Instructions

Retrieve a single form by its numeric ID. Returns full form metadata including fields, submit button, and thank-you page configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formIdYes

Implementation Reference

  • src/index.ts:99-104 (registration)
    Registration of the 'marketo_get_form_by_id' tool with the MCP server, defining its name, description, input schema (formId as number), and handler.
    server.tool(
      'marketo_get_form_by_id',
      'Retrieve a single form by its numeric ID. Returns full form metadata including fields, submit button, and thank-you page configuration.',
      { formId: z.number() },
      tool(async ({ formId }) => makeApiRequest(`/asset/v1/form/${formId}.json`, 'GET'))
    );
  • The handler function for marketo_get_form_by_id. It calls makeApiRequest with a GET request to the Marketo API endpoint /asset/v1/form/{formId}.json.
    tool(async ({ formId }) => makeApiRequest(`/asset/v1/form/${formId}.json`, 'GET'))
  • Input schema using Zod; expects a single parameter 'formId' of type number.
    { formId: z.number() },
  • The makeApiRequest helper function that handles authentication, HTTP requests to the Marketo API, and error handling. Used by the tool handler to make the GET request.
    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;
      }
    }
  • src/index.ts:55-74 (registration)
    The 'tool' wrapper function that wraps handler logic, catches errors, and formats responses as MCP content.
    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?

With no annotations, the description must self-disclose behavioral traits. It states the output is 'full form metadata' but does not mention error behavior (e.g., if ID is invalid), side effects (none expected), or any operational constraints. For a simple read operation, this is minimally adequate but not rich.

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?

Single sentence is direct and front-loaded. No redundant or extraneous information. Every word serves a purpose.

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 tool's simplicity (one parameter, no output schema), the description adequately covers purpose, input, and output. Missing elements like error handling are minor for a getter. Slightly incomplete due to lack of usage context but sufficient for basic invocation.

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 description coverage is 0%, so the description must compensate. It adds 'by its numeric ID' which reiterates the schema's type constraint. No additional meaning about the parameter's format, validation, or relationship to other data is provided.

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 ('Retrieve'), the resource ('single form'), the identifier ('by its numeric ID'), and the output ('full form metadata'). It distinguishes itself from the sibling 'marketo_get_forms' (which returns multiple forms) and other getters like 'marketo_get_email_by_id'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., 'marketo_get_forms' for listing forms, or other ID-based retrievers). Does not specify prerequisites, exclusions, or when-not-to-use scenarios.

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