Skip to main content
Glama
shutovdef-dotcom

Google Search Console MCP Server

by shutovdef-dotcom
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

gsc_build_jobposting_lifecycle_queue

Audit JobPosting schema and inspect URLs to build a safe, read-only lifecycle queue. Evaluates structured data and URL diagnostics without altering Search Console data.

Instructions

Build a read-only JobPosting lifecycle action queue.

This composes the safe JobPosting schema audit with optional URL Inspection
diagnostics. It never calls the Google Indexing API, never publishes
URL_UPDATED/URL_DELETED, never requests indexing, never writes files, and
never mutates Search Console.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYes
max_urlsNo
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses all key behavioral traits: read-only, no Indexing API calls, no URL updates, no file writes, no mutation of Search Console.

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 purpose, no extraneous verbiage.

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

Completeness5/5

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

With an output schema present, the description adequately covers the tool's composition (schema audit + URL Inspection) and safe nature, making it complete for an agent to understand when and how to invoke.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage and the tool description does not explain any parameters. Agent must infer meanings from parameter names alone; format of urls string is ambiguous.

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?

Clearly states it builds a read-only JobPosting lifecycle action queue, and distinguishes from sibling tools like build_indexing_action_queue by explicitly noting it never calls the Indexing API.

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

Usage Guidelines5/5

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

Explicitly describes when to use (for read-only queue building) and when not to use (not for actual indexing), and contrasts with sibling tools that may call the Indexing API.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shutovdef-dotcom/google-search-console-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server