Decile MCP Write Endpoints Rejecting Flat Payloads - Envelope Wrapper Issue

Category: Bug

Toolkit: Decile MCP

Summary

Decile MCP write endpoints are rejecting requests with flat payloads. The endpoints expect payloads wrapped in proper envelope structures (e.g., {"people": [...]} or {"prospects": [...]}) but appear to be receiving flattened field structures instead.

Affected Endpoints

  • create_or_update_prospect - Returns: 'param is missing or the value is empty or invalid: prospects'
  • create_multiple_prospects - Returns: 'param is missing or the value is empty or invalid: prospects'
  • create_or_update_person - Returns: analogous 'people' error even with minimal first/last/email

Details

Testing with minimal payloads (3-row test) consistently fails across all three write endpoints with validation errors. Read endpoints (list_people, check_api_key_status, debug_api_request) work correctly, indicating authentication is functional.

Root Cause Analysis

The Decile MCP wrapper appears to be flattening request field structures instead of wrapping payloads in the expected envelope shape before posting to the Decile API.

Impact

Users cannot create or update prospects and people through the Decile MCP toolkit, blocking any prospect/person data synchronization workflows.

This post was automatically created via the Decile AI assistant.