Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_approve_form

Approve a draft form to make it available for use in landing pages and embeds. Optionally include an approval comment.

Instructions

Approve a draft form, making it available for use in landing pages and embeds. Optionally include an approval comment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formIdYes
commentNo

Implementation Reference

  • src/index.ts:129-143 (registration)
    Tool registration for 'marketo_approve_form' via server.tool() on the McpServer instance. Defines name, description, schema, and handler.
    server.tool(
      'marketo_approve_form',
      'Approve a draft form, making it available for use in landing pages and embeds. Optionally include an approval comment.',
      {
        formId: z.number(),
        comment: z.string().optional(),
      },
      tool(async ({ formId, comment }) =>
        makeApiRequest(
          `/asset/v1/form/${formId}/approve.json`,
          'POST',
          comment ? { comment } : undefined
        )
      )
    );
  • The handler function wrapped by the 'tool' helper. Calls makeApiRequest to POST to the Marketo form approve endpoint, optionally including a comment.
    tool(async ({ formId, comment }) =>
      makeApiRequest(
        `/asset/v1/form/${formId}/approve.json`,
        'POST',
        comment ? { comment } : undefined
      )
    )
  • General-purpose helper that handles all Marketo API requests. Prepares headers with Bearer token, sends the request via axios, and returns response data.
    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;
      }
    }
  • Wrapper function that converts a handler's return value into MCP content blocks and catches errors to return structured error 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,
          };
        }
      };
    }
  • Input schema for the tool: formId (number, required) and comment (string, optional). Validated with Zod.
    {
      formId: z.number(),
      comment: z.string().optional(),
    },
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'making it available' but omits details like permissions required, irreversibility, or what happens if form is already approved.

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?

Two sentences, no redundant information, front-loaded with the core action and effect. Efficient and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple approve action, description covers basics but lacks context on edge cases (e.g., form not in draft) and return value. No output schema further limits completeness.

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 has 0% description coverage. The description adds minimal meaning beyond the schema: 'optionally include an approval comment' repeats comment's optionality; formId is not described. No parameter details like format or constraints.

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 ('Approve a draft form') and the effect ('making it available for use in landing pages and embeds'), distinguishing it from siblings like marketo_clone_form or marketo_get_form_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 vs alternatives (e.g., when form is not in draft, or when to use marketo_clone_form). No exclusions or prerequisites mentioned.

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