Skip to main content
Glama

Visibility Genies

Read Search Console sitemaps

get_search_console_sitemaps
Read-only

Lists the sitemaps submitted for the project's Search Console property: when each was sent and last read, how many addresses Google counted, and its errors and warnings. Submitting a sitemap is done at Google. Needs Search Console connected. Uses no credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "get_search_console_sitemaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
reasonNo
siteUrlNo
sitemapsNo
connectedNo
connectUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds cost ('Uses no credits'), an integration prerequisite, and picks up the openWorld dependency by noting the data originates from Google. It stops short of describing freshness or empty-property behavior.

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 tight sentences: what it returns, what it cannot do, what it requires and costs. The payload description is front-loaded and nothing is redundant with the title.

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 one-parameter read tool with an output schema, the description covers everything an agent needs: scope, returned fields, the submission boundary, connection prerequisite, and credit cost. Return-value detail is correctly delegated to the output schema.

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 coverage is 100% and the sole projectId parameter is fully documented in the schema, including the 'call list_projects to find one' pointer. The description only restates that the call operates on the project's property and adds no new syntax, format, or validation meaning. Baseline 3 is appropriate.

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

Purpose4/5

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

States a specific verb and resource: 'Lists the sitemaps submitted for the project's Search Console property,' and even enumerates the fields returned (sent/last read dates, URL counts, errors and warnings). The 'Search Console' qualifier plus 'sitemaps' cleanly separates it from get_search_console_performance, though the description never names a sibling to contrast with explicitly.

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?

'Submitting a sitemap is done at Google' is a genuine when-not boundary, telling the agent this tool cannot perform submission. 'Needs Search Console connected' supplies the precondition. What's missing is an explicit alternative tool for related questions (e.g. performance data), but the scope guidance is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources