Loading ToolBench
A local MCP server for Google Search Console. Speaks stdio JSON-RPC. Credentials: ADC (preferred) or service account.
gsc-mcp provides 9 well-named tools with clear descriptions (avg 120 chars) and complete JSON schemas. All tools start with action verbs (list_, get_, query_, inspect_, compare_, manage_, find_). Schemas include proper type definitions and required fields. However, parameter descriptions are sparse (many lack detail on format/constraints), output schemas are not documented, and error handling guidance is minimal. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications. Missing pagination guidance for list_sites and query_search_analytics. Overall solid foundation but lacks LLM-optimization depth.
Compare search analytics data between two time periods
Find pages with low click-through rate (CTR) compared to impressions
Find pages with declining clicks or impressions over time
Find queries where the site ranks on page 2 (positions 11-20) of search results
Get detailed information about a specific Google Search Console property
Inspect a URL in Google Search Console to get indexing and coverage information
Output schemas not documented. LLMs cannot infer what fields query_search_analytics, compare_periods, find_ctr_gaps return, forcing them to guess downstream field names and risk broken tool chains.
Parameter descriptions lack format/constraint details. 'start_date' and 'end_date' state 'YYYY-MM-DD format' but no guidance on valid ranges, timezone handling, or GSC API limits (e.g., max 90 days). LLMs cannot validate inputs without explicit constraints.
No tool annotations (readOnlyHint/destructiveHint/idempotentHint). manage_sitemaps is marked WRITE risk but lacks destructiveHint annotation. LLMs cannot distinguish safe reads from destructive writes without explicit hints.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | <=2025-11-25 | v2 |
List all Google Search Console properties accessible to the authenticated user
Manage sitemaps for a Google Search Console property (list, submit, or delete)
Query search analytics data from Google Search Console for a specific site
Pagination not addressed. list_sites and query_search_analytics may return large result sets but lack limit/offset/cursor parameters or total_count in response. LLMs cannot handle multi-page results.
Error handling guidance missing. No recovery hints in descriptions (e.g., 'If site_url is invalid, call list_sites() first'). Agents cannot self-correct on failures.