Skip to main content
Glama
Sign In
gsc-mcp

gsc-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

indexing_publish

Notify Google about an eligible URL update or removal via the Indexing API for JobPosting or BroadcastEvent livestream pages; this does not guarantee indexing.

Instructions

Notify Google about an eligible URL update or removal via the Indexing API. Google supports only JobPosting pages and livestream pages with BroadcastEvent embedded in VideoObject; this notification does not guarantee indexing.

Input Schema

NameRequiredDescriptionDefault
urlYesThe fully-qualified URL to notify about
typeYesNotification type: URL_UPDATED or URL_DELETED
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",
-  "type"
-]New value: +[
+  "url",
+  "contentType",
+  "type"
+]
  2. First observedv1.3.1

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden; it discloses the significant behavioral trait that this is a hint, not a guarantee, and that only two page types qualify. It omits operational constraints such as quota/rate limits and auth requirements, which matter for an Indexing API 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?

Two tight sentences, zero waste; the action is front-loaded and the eligibility constraint plus non-guarantee caveat follow immediately.

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 3-required-param notifier with no output schema, the description covers what the agent must know to call it correctly. Missing quota/auth context keeps it from being fully complete, but the core eligibility and expectation-setting content is present.

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% with enums for type and contentType, so the schema already defines the parameters. The description adds eligibility meaning around contentType, but no further format or sequencing guidance beyond the schema. 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?

Specific verb+resource: 'Notify Google about an eligible URL update or removal via the Indexing API.' It clearly frames a single-URL notification but never names siblings like indexing_batch_publish or url_inspection_inspect, so the agent must infer this is the single-URL variant.

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?

Gives a clear usage condition (eligible URL update or removal) plus hard eligibility limits (JobPosting pages, livestream pages with BroadcastEvent in VideoObject) and the caveat that notification does not guarantee indexing. It stops short of explicitly excluding or routing to alternatives such as batch publish or inspection.

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