Skip to main content

Troubleshoot: query_data type validation errors in Funnel MCP

Resolve Funnel MCP failures when query_data rejects parameters with type validation errors while other MCP tools still work.

Problem summary

You use Funnel MCP in Claude and query_data fails with type validation errors, while other Funnel MCP tools such as prepare_data, load_workspace and search_fields still work.

Error message or symptoms

Your MCP client may report that the query_data tool is defined with an empty parameters schema ("properties": {}). The client then serializes parameter values as strings, and query_data rejects them with type validation errors for array or object parameters such as dimensions, measures, filter, group_by, order_by and limit.

When does this occur

  • When you call query_data in Claude or another MCP client that validates tool parameter types strictly

  • When query_data worked previously but started failing without changes on your side

  • When other Funnel MCP tools in the same session work normally

Root cause

The Funnel MCP server published an incomplete parameter schema for the query_data tool. Your MCP client sends parameters in a format the tool rejects. This is a server-side issue and requires a fix from Funnel.

Solution

  1. Confirm other Funnel MCP tools work in the same session (for example list_workspaces, prepare_data, load_workspace, get_dimension_values or search_fields).

  2. Try query_data again in a new chat or session so your client reloads the tool definitions.

  3. If it still fails, disconnect and reconnect Funnel MCP in your client, complete OAuth again, then retry query_data in a new chat or session.

  4. If query_data still fails, contact Funnel support. Include:

    • Your Funnel workspace name

    • Your MCP client (for example Claude desktop or Claude Code)

    • The full error text from your MCP client

    • When the issue started

    • Confirmation that other Funnel MCP tools work

  5. Retry query_data in a new session after support confirms the fix is deployed.

Did this answer your question?