Skip to main content
Glama
shutovdef-dotcom

Google Search Console MCP Server

by shutovdef-dotcom
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

submit_sitemap

Submit a new sitemap or resubmit an existing one to Google Search Console to ensure your website content is indexed properly.

Instructions

Submit a new sitemap or resubmit an existing one to Google.

Args:
    site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
              "sc-domain:example.com"). Domain properties cover all subdomains — use the
              domain property as site_url and filter by page to analyze a specific subdomain.
    sitemap_url: The full URL of the sitemap to submit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYes
sitemap_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It explains the site_url format and domain property coverage, but does not disclose whether submission is asynchronous, overwrites existing sitemaps, or has quotas.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences plus parameter descriptions, front-loaded with purpose, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 2 required parameters and the presence of an output schema, the description adequately explains inputs. It could mention success/error behavior, but is largely complete for a submit action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description provides detailed explanations for both parameters, including examples and usage notes for site_url (e.g., domain properties covering subdomains) and a clear definition for sitemap_url.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'Submit' and the resource 'sitemap to Google', distinguishing it from sibling tools like delete_sitemap or audit_sitemap_urls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does (submit/resubmit), but does not provide explicit guidance on when to use it vs alternatives like manage_sitemaps or audit_sitemap_urls.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shutovdef-dotcom/google-search-console-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server