Skip to main content
Glama
ignytehq

plunk-mcp

Official
by ignytehq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Insert step into a connection

plunk_insert_workflow_step

Insert a step into an existing workflow connection, rewiring A→B to A→new step→B without breaking the graph.

Instructions

Purpose: Add a step in the middle of an existing connection, so A to B becomes A to the new step to B, with both connections rewired for you.

Not for: Adding a step at the end or start of a branch — plunk_add_workflow_step plus plunk_add_workflow_transition is the way to do that.

Returns: The created step including its id.

Use when: Slotting a step into a workflow that already runs. This is safer than deleting a connection and rebuilding it by hand, because the graph is never left broken partway through.

Note: Requires Plunk v0.13+. Plunk validates the resulting connections, so a change that would strand contacts is rejected rather than half-applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWorkflow UUID
nameYes
typeYesStep type. TRIGGER = entry point (auto-created with workflow). SEND_EMAIL = send a templated email. DELAY = wait X time. WAIT_FOR_EVENT = wait for a specific event with timeout. CONDITION = if/else branching. EXIT = early exit. WEBHOOK = call an external URL. UPDATE_CONTACT = update contact fields.
configYesStep-type-specific config. SEND_EMAIL: { templateId, recipient: { type: 'CONTACT' | 'CUSTOM', customEmail? } }. DELAY: { amount, unit: 'minutes'|'hours'|'days' } (max 365 days). WAIT_FOR_EVENT: { eventName, timeout? }. CONDITION: { field, operator, value? } or multi-branch shape. WEBHOOK: { url, method, headers?, body? } — url/headers/body support template variable interpolation (e.g. {{contact.email}}) on v0.12+. UPDATE_CONTACT: { updates?: {...}, subscriptionAction?: 'none'|'subscribe'|'unsubscribe' } — subscriptionAction lets a workflow change subscription state; at least one of updates or subscriptionAction is required.
positionYesUI position (e.g. {x, y})
templateIdNoEmail template UUID, for SEND_EMAIL steps.
transitionIdYesThe connection to insert into. Get it from plunk_get_workflow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds meaningful context beyond them: a version requirement (Plunk v0.13+), atomic validation that rejects changes stranding contacts rather than half-applying, and the guarantee that the graph is never left broken. It doesn't describe error types or pagination, but these are edge concerns.

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?

Bold section headers (Purpose, Not for, Returns, Use when, Note) front-load the key information and make it scannable. Every sentence earns its place, with no redundant restatement of the name.

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 mutation tool with no output schema, the description supplies the return ('the created step including its id'), the version prerequisite, and the atomicity guarantee. Nothing an agent needs to invoke it correctly is missing.

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 86%, so the schema already documents nearly all parameters including transitionId's source. The description implies that transitionId is the connection being rewired but adds no new syntax, format, or constraints beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a precise verb and resource ('Add a step in the middle of an existing connection') and even explains the graph transformation (A to B becomes A to new step to B). It differentiates itself from the sibling plunk_add_workflow_step by naming it directly as the alternative for end/start insertion.

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?

It has an explicit 'Not for' section naming the sibling tools to use instead for end/start insertion, and a 'Use when' section describing the scenario (slotting a step into an already-running workflow). Both the when and the when-not are spelled out with the alternative.

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