Skip to main content
Glama

Visibility Genies

Inspect URLs

inspect_urls
Read-only

Asks Google's URL Inspection for up to 10 URLs of the project's Search Console property: whether each is indexed, its coverage state, and the canonical Google chose. A URL that fails is reported next to the ones that worked. 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>",
      "urls": "<urls>"
    },
    "name": "inspect_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes1-10 absolute URLs to inspect. Each must belong to the project's connected Search Console property.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
languageCodeNoBCP-47 language for the messages Google returns, e.g. 'en-US'.

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
reasonNo
resultsNo
siteUrlNo
connectedNo
connectUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark it read-only and non-destructive, and the description adds meaningful behavior: a hard batch cap of 10, partial-failure handling where failed URLs are reported alongside successes, an external dependency on Search Console, and zero credit cost. What it does not cover is what an error looks like when a URL is outside the property.

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?

Short, front-loaded sentences that each carry information: capability first, failure semantics, then preconditions and cost. No filler, though the phrasing is slightly choppy and could be consolidated into fewer, denser sentences.

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?

With an output schema present, return values need not be re-explained, and annotations cover the safety profile. The description still supplies the operational essentials (batch cap, external dependency, cost, partial failure) and leaves only edge-case error behavior unstated.

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 the schema already explains urls, projectId, and languageCode. The description reinforces the 10-URL cap and property-membership constraint but adds no syntax or format detail the schema lacks (for example, the language code is never mentioned).

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 ('Asks Google's URL Inspection for up to 10 URLs') plus the exact data returned: indexed status, coverage state, and chosen canonical. It is precise about what it does, but never distinguishes itself from sibling inspection tools such as check_page_seo.

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?

Gives real preconditions: the URLs must belong to the project's connected Search Console property, Search Console must be connected, and the call uses no credits. It stops short of saying when to reach for this versus another SEO/page-checking sibling, so the agent must infer the choice.

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