Skip to main content
Glama
kotiniiqq

migrate-to-n8n

by kotiniiqq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List the zaps in a Zapier export

list_zaps
Read-onlyIdempotent

Lists zaps in a Zapier export with ID, title, step count, apps, and on/off state so users can choose which zaps to convert before conversion.

Instructions

List the zaps in a Zapier export without converting anything: id, title, number of steps, apps used and on/off state of each. Use it before convert_zapier when the export holds more than a few zaps, so the user can choose which ones to convert. Reads the file only; writes nothing.

Input Schema

NameRequiredDescriptionDefault
jsonNoThe full contents of the exported file, when the user pasted or attached it instead of giving a path. Give either path or json, not both.
pathNoAbsolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / json / description
      Previous value: -"The exported file contents, when the user pasted or attached it"New value: +"The full contents of the exported file, when the user pasted or attached it instead of giving a path. Give either path or json, not both."
    • changedInput schema / properties / path / description
      Previous value: -"Path to the exported file on this computer"New value: +"Absolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both."
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds meaningful context: it performs no conversion and reads the file only, which is the key behavioral distinction from convert_zapier. It could go slightly further on error behavior, but it exceeds the lowered bar for annotated tools.

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 with zero waste, front-loaded with the action and return fields before the usage guidance. Every sentence earns its place.

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?

Despite having no output schema, the description enumerates the returned fields (id, title, step count, apps, on/off state), so return semantics are clear. Combined with full schema coverage and comprehensive annotations, 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 description coverage is 100%, and both parameters (json vs path) are fully documented with a mutual-exclusion rule in the schema. The description adds no parameter-level detail beyond what the schema already provides, so the baseline 3 is appropriate.

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 and resource ('List the zaps in a Zapier export') and enumerates the fields returned, making it easy to distinguish from convert_zapier and the other conversion siblings. An agent can identify the tool's scope without opening the schema.

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

Usage Guidelines5/5

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

Explicitly says to use it before convert_zapier when the export holds more than a few zaps, so the user can choose which ones to convert. This names the alternative and the condition that selects it, leaving nothing to inference.

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