Hi, I am trying to use Claude to automate CRM process and came across a problem on Decile MCP. I've reported this(#122431). When will you fix it and notify me? Thank you!!!
Minimal repro: Decile MCP write endpoints fail due to missing top-level array envelope
Minimal repro: Decile MCP write endpoints fail due to missing top-level array envelope
Summary
Decile MCP read endpoints work, but multiple write endpoints fail with the same validation error indicating the wrapper is not nesting records under the required top-level key.
Decile MCP read endpoints work, but multiple write endpoints fail with the same validation error indicating the wrapper is not nesting records under the required top-level key.
Environment
- Toolkit: Decile MCP
- Auth: valid
- Confirmed working reads: list_people, check_api_key_status, debug_api_request
- Toolkit: Decile MCP
- Auth: valid
- Confirmed working reads: list_people, check_api_key_status, debug_api_request
Repro 1: createorupdate_person
Input:
json
{
"first_name": "Test",
"last_name": "User",
"email": "test@example.com"
}
Actual error:
text
param is missing or the value is empty or invalid: people
Input:
json
{
"first_name": "Test",
"last_name": "User",
"email": "test@example.com"
}
Actual error:
text
param is missing or the value is empty or invalid: people
Repro 2: createorupdate_prospect
Actual error:
text
param is missing or the value is empty or invalid: prospects
Actual error:
text
param is missing or the value is empty or invalid: prospects
Repro 3: createmultipleprospects
Actual error:
text
param is missing or the value is empty or invalid: prospects
Actual error:
text
param is missing or the value is empty or invalid: prospects
Expected behavior
Wrapper should send:
json
{ "people": [ ... ] }
or
json
{ "prospects": [ ... ] }
Wrapper should send:
json
{ "people": [ ... ] }
or
json
{ "prospects": [ ... ] }
Likely root cause
MCP wrapper posts record fields flat instead of wrapping them in the API’s required envelope.
MCP wrapper posts record fields flat instead of wrapping them in the API’s required envelope.