Why are Google Search Console MCP Tools Failing Due to Exceeding the 64-Character Limit?

This topic was automatically generated from Slack. You can find the original thread here.

Summary
Google Search Console MCP tools are failing with a “string too long” error, indicating tool names exceed a 64-character limit. This appears to be due to internal prefixing that adds ~19 characters to the actual tool name.
Environment
MCP Server: Pipedream MCP Server
Client: Claude Desktop
Date First Noticed: [Today’s date - please fill in]
Last Known Working: Yesterday [please specify exact date if known]
Description
All Google Search Console MCP tools are failing with the following error:



An error occurred while calling the tool: AI_APICallError: Invalid 'tools[1].function.name': string too long. Expected a string with maximum length 64, but got a string with length [X] instead.

Affected Tools

  1. GOOGLE_SEARCH_CONSOLE-RETRIEVE-SITE-PERFORMANCE-DATA (53 chars visible, reports as 72 chars)
  2. GOOGLE_SEARCH_CONSOLE-SUBMIT-URL-FOR-INDEXING (46 chars visible, reports as 65 chars)
    Tools That Work (for comparison)
    GOOGLE_ANALYTICS-CREATE-GA4-PROPERTY (37 characters) - Works fine
    GOOGLE_ANALYTICS-RUN-REPORT-IN-GA4 (35 characters) - Works fine
    Steps to Reproduce
  3. Attempt to call any Google Search Console MCP tool
  4. Provide valid parameters
  5. Observe the error message about string length
    Expected Behavior
    Google Search Console tools should execute successfully as they did previously.
    Actual Behavior
    Tools fail immediately with a validation error before execution.
    Analysis
    • The error shows tool names are ~19 characters longer than their visible names
    • This suggests internal prefixing (possibly “pipedream-server/” or similar) is being added
    • The 64-character limit appears to be newly enforced (worked yesterday)
    • Only Google Search Console tools are affected due to their longer base names
    Suggested Fix
  6. Shorten Google Search Console tool names to account for internal prefixing
  7. OR adjust the internal naming scheme to use shorter prefixes
  8. OR request the 64-character limit be increased
    Additional Information
    • Other MCP tools with shorter names continue to work
    • This is blocking all Google Search Console functionality
    • No workaround available as tool names cannot be modified by users
    Sample Error for Testing


json
{
  "tool": "GOOGLE_SEARCH_CONSOLE-RETRIEVE-SITE-PERFORMANCE-DATA",
  "parameters": {
    "dimensions": ["QUERY"],
    "endDate": "2025-03-31",
    "startDate": "2025-03-01",
    "rowLimit": 10
  }
}

Thanks for reporting, the team is aware of this issue

Posted thread to Discourse: Why are Google Search Console MCP Tools Failing Due to "String Too Long" Error?

Any updates on this? GSC MCP has been unusable for more than 10 days.

Posted thread to Discourse: Why are Google Search Console MCP tools failing due to "string too long" error and how can it be fixed?

This is still the issue:

Bump this, got the same issue on G calendar tool.

An error occurred while calling the tool: AI_APICallError: Invalid 'tools[1].function.name': string too long. Expected a string with maximum length 64, but got a string with length 66 instead.

Do you think it is a Google related issue, or it is just a MCP?

I’m not sure, the same request seems working in chat.pipedream.com

I tried several clients, and Windsurf and Claude Desktop always return the same error for me.

Hi , any update on this issue?

Not yet