Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

Inspect URL in Google

gsc_inspect_url
Read-only

Google index status, last crawl, canonical and rich results for one URL. Uses the property's URL Inspection quota (2,000 per day). insights_index_audit inspects many URLs in one call.

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": {
      "siteUrl": "<siteUrl>",
      "inspectionUrl": "<inspectionUrl>"
    },
    "name": "gsc_inspect_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlYesSearch Console property exactly as gsc_list_sites returns it: "https://example.com/" or "sc-domain:example.com"
languageCodeNoLanguage for messages, e.g. en-US or tr-TR
inspectionUrlYesFull URL to inspect; must belong to the property

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, not open-world), so the description's added value is the quota disclosure — 2,000 inspections per day drawn from the property's URL Inspection quota — which is a real operational constraint an agent should plan around. It does not mention failure modes (URL not in property, quota exhaustion response), leaving some behavioral gaps.

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 compact sentences with zero filler: the return payload is front-loaded, then the quota constraint, then the routing hint. Every sentence earns its place.

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 no output schema, the description correctly summarizes the returned fields and adds the cost constraint, which is enough for a three-parameter read tool. Minor missing piece is how results are shaped or what an unindexed URL returns, but nothing an agent needs in order to call it correctly is absent.

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% and the schema already explains siteUrl formatting, the URL-format pattern, and the languageCode purpose. The description adds no parameter-level detail beyond the passing reference to 'the property's URL Inspection quota', so the baseline 3 applies.

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?

States a specific verb and resource ('inspect' one URL) plus the exact payload it returns: index status, last crawl, canonical and rich results. It also names the sibling insights_index_audit as the many-URL variant, so an agent can separate the two 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 Guidelines4/5

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

Explicitly routes bulk work to insights_index_audit ('inspects many URLs in one call'), which implies this tool is the single-URL choice. There are no explicit when-not conditions (e.g. don't use for URLs outside the property, or what to do if quota is exhausted), so it stops short of a 5.

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

All mowteng toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources