← All Tools 🔎

Google Search Console

Ask your AI how people find your site on Google

4 tools available

The Search Console tools let your AI agent read the same data you see in Google Search Console. Ask which searches bring visitors, which pages get impressions but few clicks, how your average position moved this month, or why a page is not indexed — the AI runs the query and explains the numbers.

Access goes through a Google Cloud service account that you create and control, the same one the Google Analytics tools use. You add it as a user only on the sites you want to share, store its JSON key once in your private RunTools storage, and revoke it from Google at any time.

Benefits

Why use Google Search Console?

✓ Read-only: the service account can see reports but never changes your sites or submits anything

✓ Clicks, impressions, CTR and position by query, page, country, device or date

✓ URL inspection: indexing status, last crawl, canonical and robots.txt for any page

✓ Sitemap status with errors, warnings and submitted URLs

✓ One service account for both Search Console and Google Analytics

Use Cases

What can you do?

Keyword research

Find the search queries that already bring impressions and the ones where you rank on page two.

Title and description fixes

Spot pages with many impressions but a low CTR and ask your AI for better titles.

Indexing problems

Inspect a page that does not show up on Google and get the exact reason: blocked, not crawled, canonical elsewhere.

SEO reports

Combine with Google Analytics to see how people find your site and what they do once they arrive.

Getting Started

How to set up

Create a service account

In Google Cloud, enable the Google Search Console API in a project, create a service account and download a JSON key for it. If you already set up the Google Analytics tools, reuse that service account and just enable the API.

Add it to Search Console

In Search Console, open Settings → Users and permissions on each site and add the service account email (it ends in .iam.gserviceaccount.com) with Restricted permission.

Store the key

Save the whole JSON key with env_vars_set key='GOOGLE_SERVICE_ACCOUNT_JSON'. It is a secret: prefer storing it yourself over pasting it into a shared chat.

Ask your AI

Try: "List my Search Console sites and show me the top 20 search queries of the last 28 days for the first one".

Your Endpoint

Connect with Google Search Console

Use this URL to connect with only Google Search Console + Environment Variables enabled.

MCP Endpoint

https://mcp.runtools.link/{YOUR_KEY}

🔍 Brave Search

6 tools View →

🧠 Memory

9 tools View →

📄 Pandoc

2 tools View →

🌐 Web

2 tools View →

🔑 Environment Variables

3 tools View →

📑 WeasyPrint

1 tool View →

💭 Sequential Thinking

1 tool View →

🗄️ Database

6 tools View →

📁 Filesystem

11 tools View →

📧 Email

11 tools View →

👤 Account

2 tools View →

✈️ Telegram

1 tool View →

🚀 OpenRocket

12 tools View →

📊 Google Analytics

3 tools View →

🔎 Google Search Console

4 tools

🅱️ Bing Webmaster Tools

5 tools View →

Tools

Google Search Console Tools

search_console_list_sites

0 args

List the Google Search Console properties (sites) the user's service account can read, with its permission on each. Credentials are read from the GOOGLE_SERVICE_ACCOUNT_JSON environment variable (set it first with env_vars_set).

No arguments required

search_console_performance

7 args

Google Search performance of a site from Search Console: clicks, impressions, CTR and average position, grouped by any of query, page, country, device, searchAppearance or date. E.g. top search queries (dimensions ['query']), pages that get impressions but few clicks (['page']), or daily clicks (['date']). Sorted by clicks, highest first (by date when grouping only by date). Credentials are read from the GOOGLE_SERVICE_ACCOUNT_JSON environment variable (set it first with env_vars_set).

Arguments

Name	Type	Description
site_url	string	Search Console property as listed by search_console_list_sites, e.g. 'sc-domain:example.com' or 'https://www.example.com/'	required
dimensions	enum[]	How to group the rows (default ['query']). Empty for site totals Default: `["query"]`	optional
start_date	string	Start date: YYYY-MM-DD, 'today', 'yesterday' or 'NdaysAgo' (default '28daysAgo', like the Search Console UI) Default: `"28daysAgo"`	optional
end_date	string	End date, same formats (default 'today'; the last 2-3 days are still incomplete) Default: `"today"`	optional
search_type	enum	Which Google results to count (default 'web') Default: `"web"` Values: `web` `image` `video` `news` `discover` `googleNews`	optional
filters	object[]	Only count rows matching all of these, e.g. [{dimension:'page', operator:'contains', expression:'/blog/'}] Default: `[]`	optional
limit	number	Maximum rows to return (1-1000, default 50) Default: `50`	optional

search_console_inspect_url

2 args

Inspect how Google sees one URL of a Search Console site: whether it is indexed, why not, last crawl, canonical, robots.txt and rich results. Same data as the URL Inspection tool in Search Console. Credentials are read from the GOOGLE_SERVICE_ACCOUNT_JSON environment variable (set it first with env_vars_set).

Arguments

Name	Type	Description
site_url	string	Search Console property as listed by search_console_list_sites, e.g. 'sc-domain:example.com' or 'https://www.example.com/'	required
url	string	Full URL to inspect; it must belong to site_url, e.g. 'https://www.example.com/pricing'	required

search_console_sitemaps

1 arg

List the sitemaps submitted to Search Console for a site, with when Google last read them, errors, warnings and how many URLs each one submits. Credentials are read from the GOOGLE_SERVICE_ACCOUNT_JSON environment variable (set it first with env_vars_set).

Arguments

Name	Type	Description
site_url	string	Search Console property as listed by search_console_list_sites, e.g. 'sc-domain:example.com' or 'https://www.example.com/'	required

Explore More

Other Tool Categories

Discover more tools to supercharge your AI agent

🔍

Brave Search

Web, image, video, news, and local search powered by Brave. AI-powered summaries available.

6 tools 🧠

Memory

Persistent knowledge graph for AI agents. Store entities, relations, and observations across sessions.

9 tools 📄

Pandoc

Universal document conversion between formats: Markdown, HTML, LaTeX, Word, and 40+ more.

2 tools 🌐

Web

Web search with automatic provider fallback and URL fetching to markdown.

2 tools 🔑

Environment Variables

Persistent key-value storage for your AI agent. Store API keys, configs, and settings securely.

3 tools 📑

WeasyPrint

Convert HTML/CSS to PDF. Generate invoices, reports, tickets, or any styled document.

1 tool 💭

Sequential Thinking

Dynamic problem-solving through sequential thoughts. Break down complex problems, revise thinking, and branch into alternative approaches.

1 tool 🗄️

Database

Connect to MySQL, PostgreSQL, Redis, MongoDB, ClickHouse, or Elasticsearch and execute queries or commands. Connection URLs are stored securely via env_vars_set (MYSQL_URL, POSTGRES_URL, REDIS_URL, MONGODB_URL, CLICKHOUSE_URL, ELASTICSEARCH_URL).

6 tools 📁

Filesystem

Sandboxed file management. Read, write, edit, move, search, and organize files in your private storage.

11 tools 📧

Email

Send emails via SMTP. Configure multiple SMTP servers, create reusable templates with variables, send single or bulk emails with HTML support, and track delivery logs.

11 tools 👤

Account

View your runtools.link account information and manage your plan. Get your user hash, check your current plan, and request a Pro upgrade.

2 tools ✈️

Send messages to any Telegram chat, group or channel with your own bot. The bot token travels with each call and is never stored.

1 tool 🚀

← View All Tools