Skip to main content
Glama

search_console_sitemaps_submit

Submit a sitemap URL to Google Search Console for a verified site to register or refresh the entry and trigger a recrawl. Requires verified site ownership.

Instructions

Submit a sitemap URL to Google Search Console for the given verified site. Mutates Search Console state — registers or refreshes the sitemap entry so Google will re-crawl it. Safe to call repeatedly: re-submitting the same feedpath re-queues a crawl without creating a duplicate entry (Search Console PUTs the sitemap URL, not POST). Returns {status: 'submitted', sitemap: } on success; the API gives no synchronous processing status. Does not fetch or validate the sitemap contents — that happens asynchronously on Google's side and the parsed results surface in search_console_sitemaps_list afterwards. Requires the authenticated user to be a verified owner or full user of site_url. For read-only inspection of already-submitted sitemaps use search_console_sitemaps_list; for per-URL indexing diagnostics use search_console_url_inspection_inspect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYesProperty identifier as registered in Search Console. For URL-prefix properties use the full URL including trailing slash (e.g. 'https://example.com/'). For Domain properties use the 'sc-domain:' prefix (e.g. 'sc-domain:example.com').
feedpathYesAbsolute URL of the sitemap to submit (e.g. 'https://example.com/sitemap.xml'). Must be on the same host as site_url and reachable to Googlebot over HTTPS.
Behavior5/5

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

No annotations exist, so description carries full burden. It clearly states that the tool mutates state, is idempotent (PUT re-queues crawl), does not validate sitemap contents, and returns a simple status object. Authentication requirements are also specified.

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?

Concise at ~150 words with clear sentence structure. Core purpose is front-loaded, followed by important behavioral details, then alternatives. No redundant information.

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

Completeness5/5

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

For a mutation tool with no output schema, the description covers action, behavior, prerequisites, alternatives, and return format. All critical information for correct agent invocation is present.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds value by explaining the site_url format variations (URL-prefix vs Domain) and feedpath constraints (same host, HTTPS). Examples are provided, going beyond schema descriptions.

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?

The description clearly states the tool submits a sitemap URL to Google Search Console, using a specific verb and resource. It distinguishes from sibling tools like search_console_sitemaps_list (read-only inspection) and search_console_url_inspection_inspect (per-URL diagnostics).

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

Usage Guidelines5/5

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

Provides explicit when-to-use and when-not-to-use guidance: alternatives for read-only inspection and per-URL diagnostics are named. Also explains safe re-submission behavior and prerequisites (verified owner/full user of site_url).

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/logly/mureo'

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