Skip to main content
Glama
Sign In
gsc-mcp

gsc-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

indexing_get_metadata

Retrieves Indexing API notification metadata for an eligible JobPosting or BroadcastEvent URL, showing notification history while not confirming whether Google indexed the page.

Instructions

Get the latest Indexing API notification metadata for an eligible JobPosting or BroadcastEvent URL. This reports notification history, not whether Google indexed the URL.

Input Schema

NameRequiredDescriptionDefault
urlYesThe fully-qualified URL to check notification status for
contentTypeYesEligible structured-data type on the page: JobPosting, or BroadcastEvent embedded in VideoObject

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.6
    • addedInput schema / properties / contentType
      Added value: +{
+  "description": "Eligible structured-data type on the page: JobPosting, or BroadcastEvent embedded in VideoObject",
+  "enum": [
+    "JobPosting",
+    "BroadcastEvent"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • changedInput schema / required
      Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "contentType"
+]
  2. First observedv1.3.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does useful work by clarifying that this reports notification history, not whether Google indexed the URL. 'Get' implies a read operation, but auth requirements, rate limits, and exact response behavior are not described.

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?

Two sentences, front-loaded with the core action and immediately followed by the key caveat. Every sentence earns its place and there is no redundant filler.

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?

For a simple two-parameter read tool, the description provides enough context to select and invoke it correctly, including the important limitation about notification history versus indexing status. The absence of an output schema means return fields are not detailed, but the description still gives a useful high-level account of what is returned.

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 both parameters are already fully documented in the schema. The description reinforces the eligible content types but adds no format or usage detail beyond what the structured parameter descriptions provide.

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 states a specific verb and resource: getting the latest Indexing API notification metadata for eligible JobPosting or BroadcastEvent URLs. It also explicitly distinguishes the result from indexing status, which prevents confusion with sibling inspection tools.

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?

The eligibility constraint (JobPosting or BroadcastEvent URL) and the caveat that it reports notification history rather than indexed status give clear usage context. It does not explicitly name the alternative tool for checking indexing status, so it falls short of full when-to-use routing guidance.

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

Deploy Server

Other Tools