Skip to main content
Glama

Vee3

by io.github.Vee3io

google-search-console.submit_sitemap

Submit a sitemap URL to Search Console for a verified property.

Call google-search-console.list_sites to discover sites. Omit site_url to use the default property, or pass an exact site_url from that response. feed_path must be the full sitemap URL hosted on that property.

Cost = 10 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlNoOptional property URL from google-search-console.list_sites. When omitted, the default property is used. The user or agent passes an exact site_url value from that response.
feed_pathYesFull sitemap URL for the property, for example https://example.com/sitemap.xml.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlNoSearch Console property URL used for the request.
feed_pathNoSitemap URL that was submitted.
submittedNoTrue when Search Console accepted the sitemap submission.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / site_url / description
      Previous value: -"Optional verified property URL from google-search-console.list_sites. When omitted, the default property is used. The user or agent passes an exact site_url value from that response."New value: +"Optional property URL from google-search-console.list_sites. When omitted, the default property is used. The user or agent passes an exact site_url value from that response."
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It provides useful context: the target must be a 'verified property' and calls cost '10 tokens,' plus requires feed_path be hosted on that property. However, it does not explain what happens on duplicate submission, permission requirements, or error/response behavior, leaving a moderate transparency gap.

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?

Three short, front-loaded paragraphs: action, param guidance, cost. No filler; every sentence contributes.

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 two-parameter tool with an output schema, the description supplies the prerequisite discovery step, default property behavior, exact site_url matching, and full feed_path requirement. No critical invocation detail is missing; the output schema covers return values.

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 covers both parameters comprehensively (site_url's default/null semantics and feed_path's full-URL example), so baseline is 3. The description restates the same rules and adds only the workflow pointer to list_sites and 'hosted on that property,' which is marginal added value.

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 opens with a concrete action and object: 'Submit a sitemap URL to Search Console for a verified property.' This clearly names the verb and resource, and the sibling contrast (delete_sitemap, list_sitemaps, add_site) is implicitly resolved by 'submit sitemap' rather than add/delete/list operations.

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

Usage Guidelines4/5

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

It gives a clear precondition and workflow: 'Call google-search-console.list_sites to discover sites... Omit site_url... or pass an exact site_url...' This tells an agent how to obtain and fill valid inputs. It does not explicitly name alternative tools or exclusions, so it misses a 5.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources