Skip to main content
Glama

MetricPort

Inspect URL

gsc_inspect_url
Read-onlyIdempotent

Google index status for one URL: verdict, coverage state, last crawl, canonical, mobile usability, rich results.

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": {
      "property": "<property>",
      "url": "<url>"
    },
    "name": "gsc_inspect_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
propertyYesSearch Console property id from list_properties, e.g. sc-domain:example.com or https://www.example.com/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the return-field inventory, which is genuinely useful, but says nothing about quota limits, auth scopes, or rate constraints for a live URL-inspection call.

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?

A single compact sentence, front-loaded with the purpose and then the returned fields. No filler, no restatement of the title, every token carries information.

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

Completeness3/5

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

With no output schema, the description does the right thing by listing the return fields, which is sufficient for the response side. However, it leaves the gsc_index_check overlap unresolved and omits any auth or eligibility context for a tool that requires a specific Search Console property.

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 50% (only 'property' is documented; 'url' relies on format=uri). The description adds no parameter-level meaning, neither explaining how 'property' relates to the URL's domain nor what form the URL must take, so it neither compensates for nor worsens the coverage gap. Baseline 3.

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+resource ('Google index status for one URL') and enumerates the fields returned (verdict, coverage state, last crawl, canonical, mobile usability, rich results). It is clear what the tool does, but it does not differentiate itself from the close sibling gsc_index_check, which an agent will likely confuse it with.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as gsc_index_check or gsc_search_analytics. The only contextual link (property comes from list_properties) lives in the schema, not the description.

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.