Skip to main content
Glama
kotiniiqq

migrate-to-n8n

by kotiniiqq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

How to replace a Make module or Zapier step

suggest_replacement
Read-onlyIdempotent

Explains how one Make module or Zapier step maps to n8n: whether it converts automatically or needs an n8n app node, API HTTP request, or Code node, plus setup steps.

Instructions

Explain how one Make module or Zapier step is handled, without converting a file: whether it converts automatically and to which n8n node, or which n8n app node, HTTP request to the app's API, or Code node to use instead, with the steps to set it up. Use it when the user asks about a single module, or to explain a step a report marked review or manual.

Input Schema

NameRequiredDescriptionDefault
moduleYesThe module or step key exactly as the export or the report shows it, e.g. "slack:CreateMessage" for Make or "SlackCLIAPI:channel_message" for Zapier.
sourceYesWhere the module comes from: "make" or "zapier".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / module / description
      Previous value: -"The module or step key as it appears in the export or report"New value: +"The module or step key exactly as the export or the report shows it, e.g. \"slack:CreateMessage\" for Make or \"SlackCLIAPI:channel_message\" for Zapier."
    • addedInput schema / properties / source / description
      Added value: +"Where the module comes from: \"make\" or \"zapier\"."
  2. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world; the description adds the meaningful behavioral fact that nothing is converted or written, it only explains. It does not discuss lookup failures or what happens when a module is unknown, but the safe-read profile is clear.

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?

Purpose is front-loaded in the opening clause, and the second sentence is pure usage routing. The first sentence is dense and long with a triple enumeration, but every clause carries information and nothing is padding.

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

Completeness5/5

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

For a two-parameter read-only lookup with a fully described schema and no output schema, the description covers the input contract, the trigger, and the categories of answer (auto-conversion, app node, HTTP request, Code node plus setup steps). An agent has everything needed to call it correctly.

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?

Schema coverage is 100% and both parameters (module key format, source enum) are fully documented in the schema itself. The description adds no format or casing guidance beyond that, so the baseline 3 applies.

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?

States a specific verb ("Explain") and a specific resource (one Make module or Zapier step), and immediately scopes it against the conversion siblings with "without converting a file." It also enumerates the possible answers, so an agent knows the shape of what it gets back.

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

Usage Guidelines4/5

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

Gives two concrete triggers: the user asks about a single module, or a report marked a step as review/manual. The "without converting a file" clause implicitly routes bulk conversion to convert_make/convert_zapier, but the siblings are never named and there is no explicit when-not-to-use statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools