Skip to main content
Glama
Sign In

Google Search Console MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Request URL removal in Google Search Console

google_search_console_request_url_removal
Read-onlyIdempotent

Request URL removal in the user's own Google Search Console account from ChatGPT, Claude or any AI agent. Returns how to do it in Google Search Console step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Google Search Console Cloud Browser. Google Search Console's official API: Google Search Console has an API, but it covers only part of the web interface (checked 16 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "google_search_console_request_url_removal"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description still adds real value by stating it 'opens nothing by itself' and describing the return as step-by-step UI instructions. It does not state prerequisites such as the user needing an authenticated Cloud Browser session on the right property.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core workflow is front-loaded, but 'Google Search Console' is repeated four times and the final API sentence with a future 'checked 16 Oct 2026' date is confusing and of unclear value to the caller. Tightening would improve it materially.

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 zero-parameter, no-output-schema guidance tool, the description covers what it returns and how it relates to the browser tools that perform the actual action. Only the authentication/property preconditions are left implicit.

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

Parameters4/5

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

The tool takes no parameters, so the schema imposes nothing to explain and the baseline of 4 applies. The description correctly implies a parameterless, context-free invocation.

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?

The description states a concrete deliverable: step-by-step instructions (screens, buttons, fields) for requesting URL removal in the user's own Search Console account. It explicitly resolves the ambiguity created by the tool name by saying it 'opens nothing by itself', distinguishing it from the cotlet_browser_* action tools. Slightly muddied by the trailing API-coverage sentence, which is about Search Console generally rather than this tool.

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 two-step workflow: call this to learn the procedure, then execute it with cotlet_browser_* in the user's Cloud Browser. It does not explicitly exclude sibling GSC tools (request_indexing, list_not_indexed_urls) or say when removal guidance is not appropriate, so it stops short of full when/when-not coverage.

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

All Google Search Console MCP Server and API by Cotlet 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