google ads location area information#1918

Currently, when accessing gpt or claude through ‘windsor’ and conducting advertising operations on the ‘google ads’ account, the tools of the mcp plan of the selected ‘windsor’ service do not have the function of targeting regions. However, when conducting advertising placement operations on ‘google ads’, regions must be selected. Therefore, one can only go to the ‘google ads’ backend to select the region, which is too troublesome. It would be best to directly complete this function with one click through ‘windsor’ without having to go to the ‘google ads’ platform for other operations. Therefore, the region orientation parameter needs to be added in the tools of mcp in ‘windsor’. Enable ai to directly obtain regional information and conduct precise advertising placement

campaign_criterion_location_canonical_name, campaign_criterion_location_country_code, campaign_criterion_location_name, campaign_criterion_location_target_type were added for you

Hi Windsor.ai team,

Thank you for the update on ticket #1918 and for adding the new location fields (campaign_criterion_location_canonical_name, campaign_criterion_location_country_code, campaign_criterion_location_name, campaign_criterion_location_target_type).

I’ve confirmed on my end that these fields are available for reading via get_data, which is great. However, I wanted to double-check: are these read-only reporting fields, or is there also a corresponding write action (e.g. something like set_campaign_location) available via execute_action for setting or updating a campaign’s geo-targeting?

I checked the current list_actions output for the google_ads connector and didn’t see any location-related write action there, so I want to confirm whether this is expected, or whether write support is still in progress.

If geo-targeting write support isn’t available yet, I’d like to request it as a feature — the ability to set/update a campaign’s location targeting (e.g. by country, region, or city) via execute_action would be very valuable for our workflow, since right now we have to configure this manually in the Google Ads UI after creating campaigns through Windsor.

Thanks again for your help, and looking forward to your reply.

Best regards