Problem

MCP tools that have no parameters (e.g., browser_snapshot) were failing export validation with errors:

• "Manual parameter config mode requires parameters array to be set"
• "Manual parameter config mode requires parameterValues to be configured"

Current Behavior

1. User creates workflow with parameter-less MCP tool (e.g., browser_snapshot)
2. Node has parameters: [] and parameterValues: {} (valid empty state)
3. ❌ Export validation fails
4. ❌ User cannot export workflow to slash commands

Expected Behavior

1. User creates workflow with parameter-less MCP tool
2. Node has parameters: [] and parameterValues: {} (valid empty state)
3. ✅ Export validation passes
4. ✅ Workflow exports successfully

Solution

Modified validation logic in validate-workflow.ts to allow empty arrays/objects for parameter-less tools.

Changes

File: src/extension/utils/validate-workflow.ts (Lines 427-444)

Before:

if (!mcpData.parameters || mcpData.parameters.length === 0) {
  errors.push({ ... }); // Rejects empty array
}
if (!mcpData.parameterValues || Object.keys(mcpData.parameterValues).length === 0) {
  errors.push({ ... }); // Rejects empty object
}

After:

// Allow empty array for parameter-less tools
if (!mcpData.parameters) {
  errors.push({ ... });
}
// Only check parameterValues if parameters exist
if (mcpData.parameters && mcpData.parameters.length > 0) {
  if (!mcpData.parameterValues || Object.keys(mcpData.parameterValues).length === 0) {
    errors.push({ ... });
  }
}

Logic:

• parameters: [] is now valid (parameter-less tools)
• parameterValues: {} is valid when parameters is empty
• parameterValues existence is only checked when parameters has items

Impact

• UX: Users can now export workflows with parameter-less MCP tools
• Breaking Change: None - validation is more permissive
• Side Effects: None - tools with parameters still require values

Testing

• Manual E2E testing completed
  • Created workflow with browser_snapshot (no parameters)
  • Verified export succeeds with parameters: [] and parameterValues: {}
  • Verified tools with parameters still require values
• Code quality checks passed
  • npm run format && npm run lint && npm run check
  • npm run build succeeded

Notes

• This fix enables creation of README hero image workflow using browser_snapshot
• Export service already handles empty parameters correctly (lines 418-445)
• Validation was the only blocker

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com