Hey ​@Greg Eiselt 👋

I did some digging and found a similar report of that error for another person that was using GA4 with Zapier MCP. In that instance the issue was that they had set the Account field to “Have AI select/generate a value for this field” and the LLM didn’t send a value for the Account, which is a required field.

Are there any required fields like the Account field that don’t have a specific value set? If so, and you don't need the LLM to guess the value, can you chose the Set a specific value for this field option and select a specific value instead?

Keep us posted on how it goes, want to make sure this gets sorted! 🙂

Hi Sam,

Thanks for checking!

Can confirm that I’ve specified Account/Property/Data Stream where possible and still receive the same errors:

It looks like it’s the “Run Report for Property” action that is throwing errors. All three other actions are able to be run without issue.

Greg

Thanks for confirming that ​@Greg Eiselt. And sorry for the delay in my reply here!

Ah ok, so the Run a Report for a Property action has these required fields: 

Given that two of them are date fields it could be that the dates were supplied in the incorrect format 🤔 The format it’s expecting would be YYYY-MM-DD.

Can you confirm whether when it errored, those three required fields definitely had a value, and they were in the correct format?

Hi ​@SamB 

I can confirm the issue still persists. Tried setting all the values with the right formats but still receiving this error specified above.

Sorry to hear you’re also experiencing issues with this ​@Umer4.

To help narrow down whether it’s an issue to do with the Run Report for a Property action or MCP specifically can you set up a Run Report for a Property action directly in a Zap (without MCP) and test it?

• If the same error appears, then it could be a bug with the Run Report for a Property action. 

• If it doesn’t error, and the settings/values is the same as what’s been used for the MCP version then there might be an issue specific to how MCP is calling that Google Analytics action.

In either case it might be best to reach out to our Support Team to help investigate things further in case there’s a bug with the Run Report for a Property action or MCP. But please do report back here to share on how you get on.
 

​@Greg Eiselt - did changing the date format work in your case, or are you still running into the same error? If it didn’t work can you also try testing the same action in a Zap and let us know how that goes?

Thanks ​@SamB, for responding. Initially i though the Client(Claude) would set the account and property itself that’s why the issue was there. But when I set the account id and property id my self it resolved. 

No worries ​@Umer4. I’m so pleased you were able to get it sorted by selecting a specific value for the Account and Property IDs - nice one! 🙌