mcp-server-gsc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_capabilitiesA | List every tool this Google Search Console server offers and report authentication status. Call this first if unsure what is available. |
| reauthenticateA | Discard stored Google credentials and re-run the OAuth browser login. Use this to switch Google accounts or fix authentication errors. Opens a browser window and waits up to 5 minutes. |
| list_propertiesA | List all Google Search Console properties the authenticated account can access, with permission levels. |
| get_site_detailsA | Get details about a specific Search Console property (verification status and permission level). |
| get_search_analyticsB | Get top search queries and pages with clicks, impressions, CTR and average position for a time period. Without explicit dimensions it returns both top queries and top pages. |
| get_performance_overviewB | Summary of site search performance for a period: overall totals, daily trend, and top 5 queries and pages. |
| compare_search_periodsB | Compare search performance between two time periods: overall totals with absolute and percentage changes, plus an optional per-dimension breakdown of the biggest movers. |
| get_search_by_page_queryB | Get the search queries driving traffic to one specific page, with clicks, impressions, CTR and position. |
| get_advanced_search_analyticsC | Search analytics with full control: filter by country, device, query text, or page URL; choose search type (web, image, video, news, discover), aggregation, data state, and pagination. |
| inspect_url_enhancedA | Detailed crawl and index status for one URL: verdict, coverage state, robots.txt state, canonicals, last crawl time, rich results and mobile usability. |
| batch_url_inspectionB | Inspect up to 10 URLs at once, returning crawl/index status for each. |
| check_indexing_issuesA | Check multiple URLs for indexing problems (not indexed, blocked by robots.txt, noindex, fetch errors, canonical mismatches) and return a summary plus per-URL diagnosis. |
| get_sitemapsA | List all sitemaps submitted for a property (path, last submitted/downloaded, pending status, error and warning counts). |
| list_sitemaps_enhancedA | Detailed sitemap information including errors, warnings, type, and per-content-type submitted/indexed counts. Optionally list the children of a sitemap index. |
| manage_sitemapsA | Submit a sitemap, delete (unsubmit) a sitemap, or fetch the status of one specific sitemap. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools are distinct (e.g., get_search_analytics vs. get_search_by_page_query vs. get_advanced_search_analytics), but some overlap exists: get_performance_overview and get_search_analytics both return top queries/pages, and get_sitemaps vs. list_sitemaps_enhanced vs. manage_sitemaps have similar names and overlapping data. Descriptions help clarify but not perfectly.
The naming generally follows a verb_noun pattern (get_capabilities, list_properties, check_indexing_issues, compare_search_periods). However, there are minor deviations like get_search_by_page_query (which is not as clean as get_search_analytics), list_sitemaps_enhanced vs. get_sitemaps (list vs. get inconsistency), and manage_sitemaps (generic verb). Overall, it's mostly consistent.
15 tools for a Google Search Console server is well-scoped. It covers authentication, properties, search analytics, indexing, URL inspection, and sitemaps. Each tool serves a distinct functional area, and 15 is within the ideal range for a comprehensive domain.
The tool surface covers core GSC workflows: property management, search analytics, URL inspection, and sitemap management. However, there is no tool for managing user permissions or creating properties (though get_site_details implies existence). Also, no tool for accessing Search Console's structured data validation or security issues, but those are niche. The missing pieces are minor and agents can work around them.