Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_console_sitemaps_submit

Submits a sitemap URL to Google Search Console so Google re-crawls it. Re-submitting the same feedpath re-queues the crawl without creating duplicate entries.

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

NameRequiredDescriptionDefault
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
approvalNoExternal approval this change carries out (recorded and shown, never verified)
expectedNoExpected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.
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.
site_urlNoProperty 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').
decision_idNoA proposed decision this change carries out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.33.0
    • changedInput schema / properties / expected / description
      Previous value: -"Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."New value: +"Expected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."
  2. Changed1 schema field changedv0.28.0
    • addedInput schema / properties / approval
      Added value: +{
+  "additionalProperties": false,
+  "description": "External approval this change carries out (recorded and shown, never verified)",
+  "properties": {
+    "approved_at": {
+      "maxLength": 64,
+      "type": "string"
+    },
+    "approved_by": {
+      "maxLength": 80,
+      "type": "string"
+    },
+    "reference": {
+      "maxLength": 128,
+      "type": "string"
+    }
+  },
+  "required": [
+    "reference",
+    "approved_by",
+    "approved_at"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changedv0.26.0
    • addedInput schema / properties / decision_id
      Added value: +{
+  "description": "A proposed decision this change carries out.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / expected
      Added value: +{
+  "description": "Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.",
+  "maxItems": 12,
+  "type": "array"
+}
  4. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  5. Changed2 schema fields changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / required
      Previous value: -[
-  "site_url",
-  "feedpath"
-]New value: +[
+  "feedpath"
+]
  6. Addedv0.9.12
  7. Removedv0.9.6
  8. Addedv0.9.2
  9. Removedv0.9.1
  10. Addedv1.0.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does it well: it declares the mutation ("Mutates Search Console state"), the idempotency mechanism (PUT semantics, no duplicate entry), the exact return payload, the absence of synchronous status, and the non-validation of sitemap contents. It also states the permission prerequisite (verified owner or full user of site_url). The only gap is failure behaviour — what happens when the property is unverified or the feedpath host mismatches is not described.

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

Conciseness4/5

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

Front-loaded with the action and mutation warning, then idempotency, then return shape, then alternatives — a logical ordering with no filler sentences. It is dense and long for a single paragraph, though each clause (PUT vs POST, async parsing, permission requirement) earns its place.

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?

Despite six parameters, nested objects, and no output schema, nothing an agent needs is missing: return shape is given inline, async timing is explained, idempotency and permission constraints are stated, and the follow-up tool for parsed results is named. Complete for the complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so feedpath, site_url, reason, approval, expected and decision_id are already documented in structured form; baseline is 3. The description reinforces feedpath's same-host/HTTPS constraint and attaches the ownership requirement to site_url, but adds no new meaning for the journaling parameters.

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 opening sentence gives a specific verb and resource ("Submit a sitemap URL to Google Search Console") plus the scoping condition ("for the given verified site"). It goes on to differentiate itself from the two nearest siblings, sitemap listing and URL inspection, so an agent can route without opening either schema.

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?

It names both alternatives explicitly: read-only inspection goes to search_console_sitemaps_list, per-URL indexing diagnostics go to search_console_url_inspection_inspect. It also states the repeat-call condition ("Safe to call repeatedly ... re-queues a crawl without creating a duplicate"), covering when-not-to-worry rather than leaving it to inference.

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

Deploy Server

Other Tools