Skip to main content
Glama
Sign In

Google Search Console MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get links report in Google Search Console

google_search_console_get_links_report
Read-onlyIdempotent

Get links report 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_get_links_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely non-obvious behavior: the tool "opens nothing by itself" and returns only procedural guidance (screens, buttons, fields), which an agent could easily misread from the name as a data-fetch. The API-coverage caveat further explains why the browser path is needed.

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 message (returns instructions, then use browser tools) is front-loaded and useful, but the text pads itself with promotional framing ("from ChatGPT, Claude or any AI agent"), repeats "Google Search Console" three times, and tacks on a dated aside ("checked 16 Oct 2026") that adds little for an agent.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does so at a high level (step-by-step screens/buttons/fields). It omits any detail about the shape or length of the returned guidance and does not mention the sibling guide tool, but nothing essential for calling it correctly is missing.

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 zero parameters, so the schema imposes no semantic burden and the baseline of 4 applies. The description correctly implies no inputs are needed, though it never explicitly says the call is parameterless.

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?

States a specific verb and resource ("Get links report in the user's own Google Search Console account") and clarifies that the tool returns step-by-step UI instructions rather than the report data itself. It does not clearly distinguish itself from the sibling cotlet_app_guide, which appears to serve a similar guide role, leaving some ambiguity about which to pick.

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 sequences usage: call this to get the steps, then execute them with the cotlet_browser_* tools in the Cloud Browser. That is concrete when-to-use guidance for a multi-step workflow. It stops short of stating when not to use it or why one would choose it over cotlet_app_guide.

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