The Sitemaps category of the Google Search Console MCP server exposes 1 Google Search Console tool you can call directly from Claude, ChatGPT, or any MCP client through Weave Legal. Each Sitemaps tool below is documented with its purpose and complete input and output schema, giving your firm governed, auditable access to Google Search Console sitemaps data.
The sitemaps submitted for a property, with their submission and processing status.
We're Adding More Google Search Console Tools Constantly!
Don't see a specific Google Search Console tool you need? Email [email protected] and we can add it.
Google Search Console Frequently Asked Questions
What are the Google Search Console Sitemaps tools?
This page lists the Sitemaps tools in the Google Search Console integration: 1 tool for working with sitemaps. Each is exposed through your firm's Weave MCP connection and available to members whose access level permits it.
Why does list-sitemaps show no data for our property?
If the connected Google account can't verify the property, the tool returns no data rather than an error, confirm the siteUrl first with gsc_list-properties.
What is the Google Search Console integration?
The Google Search Console integration connects your firm's Google Search Console account to Weave. Google Search Console is Google's free tool for tracking how your sites perform in Google Search. This integration lets your AI workflows read that data, search traffic and rankings, index coverage and URL inspection, and sitemap status, for the properties your connected Google account can access. It groups 10 tools into 4 categories, exposed through your firm's Weave MCP connection and filtered per member by access level.
How does my firm connect Google Search Console to Weave?
An admin authorizes a Google account with access to your Search Console properties once, via Google's OAuth consent flow in the Weave console. Every firm member then works through that single connection, there is no per-member Google sign-in.
Why did a tool return no data for our site?
Every gsc tool that takes a siteUrl requires the connected Google account to be a verified owner or user of that property in Search Console, if it can't verify the property, the tool returns no data rather than an error. gsc_list-properties is the exception: it takes no input and simply lists every property the connected account can access, so start there to get the right siteUrl.
Why does the data look a couple of days behind our live traffic?
Search Console's performance data typically lags live traffic by about two days; that's a Google-side reporting delay, not a Weave sync issue.
Can these tools change anything in Search Console?
No. Every gsc tool is read-only, none of them can submit URLs, edit sitemaps, or change any Search Console setting.
Related Categories