Skip to main content
Glama
alexleventer

Marketo MCP Server

by alexleventer

marketo_clone_form

Clone a Marketo form into a specified folder, creating a draft that requires approval before use.

Instructions

Clone an existing form into a destination folder. The cloned form is created in draft status and must be approved before use.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formIdYes
nameYes
descriptionNo
folderIdYes

Implementation Reference

  • The handler function that executes the 'marketo_clone_form' tool logic. It calls makeApiRequest to POST to /asset/v1/form/{formId}/clone.json with the name, description, and folder as form-urlencoded data.
    tool(async ({ formId, name, description, folderId }) =>
      makeApiRequest(
        `/asset/v1/form/${formId}/clone.json`,
        'POST',
        {
          name,
          description,
          folder: JSON.stringify({ id: folderId, type: 'Folder' }),
        },
        'application/x-www-form-urlencoded'
      )
    )
  • Zod schema defining the input parameters for marketo_clone_form: formId (number), name (string), description (optional string), and folderId (number).
    {
      formId: z.number(),
      name: z.string(),
      description: z.string().optional(),
      folderId: z.number(),
  • src/index.ts:106-127 (registration)
    Registration of the 'marketo_clone_form' tool on the MCP server using server.tool(), with name, description, schema, and handler.
    server.tool(
      'marketo_clone_form',
      'Clone an existing form into a destination folder. The cloned form is created in draft status and must be approved before use.',
      {
        formId: z.number(),
        name: z.string(),
        description: z.string().optional(),
        folderId: z.number(),
      },
      tool(async ({ formId, name, description, folderId }) =>
        makeApiRequest(
          `/asset/v1/form/${formId}/clone.json`,
          'POST',
          {
            name,
            description,
            folder: JSON.stringify({ id: folderId, type: 'Folder' }),
          },
          'application/x-www-form-urlencoded'
        )
      )
    );
Behavior4/5

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

With no annotations provided, the description correctly discloses that the result is in draft status and requires approval. This adds behavioral context beyond what the schema provides. No contradictions are present.

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 concise sentences: the first covers the primary action and target, the second adds a critical behavioral note. No extraneous content.

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?

The description lacks information about return values, error conditions, or success/failure indicators. Given the absence of an output schema and low parameter documentation, the description does not provide sufficient context for complete tool understanding.

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?

The input schema has 0% description coverage. The tool description only mentions 'destination folder' without explaining each parameter's meaning (e.g., formId, name, description, folderId). This leaves the agent to infer from parameter names alone.

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 ('Clone'), resource ('existing form'), and target ('destination folder'). It distinguishes itself from sibling tools like marketo_approve_form or marketo_get_form_by_id by specifying the cloning operation.

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 notes that the clone is created in draft status and must be approved, implying a workflow with marketo_approve_form. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide prerequisites or exclusions.

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