GSC SEO MCP has 4 well-named tools with complete input schemas and descriptions. Tool names follow verb_noun convention (gsc_list_*, gsc_search_*, gsc_inspect_*). All tools have descriptions (avg 95 chars, within 10-1024 range). Input schemas are properly typed with nested objects for complex params (e.g., filters array with group_type and dimension objects). However, output schemas are NOT documented in the source code, only input schemas are visible. Parameter descriptions are present but minimal (avg 45 chars); many lack format/constraint details. No error handling guidance visible. No tool annotations (readOnlyHint, etc.) despite all tools being READ_ONLY. Missing pagination guidance for gsc_search_analytics which could return large result sets.
Inspect a URL in Google Search Console to get indexing status and other insights.
List all sitemaps submitted to a Search Console property.
List all Search Console properties accessible to the authenticated user.
Query Search Analytics data for a Search Console property.
Output schemas not documented. LLMs cannot plan downstream tool calls or extract fields without knowing response structure.
Tool annotations missing. All 4 tools are READ_ONLY but lack readOnlyHint annotation, preventing clients from optimizing caching/retry logic.
gsc_search_analytics lacks pagination guidance. No row_limit default, no total_count in response spec, no next_cursor pattern documented.
Parameter descriptions lack format/constraint details. 'start_date' says 'YYYY-MM-DD format' but no validation guidance. 'dimensions' array lacks enum of valid values (query, page, device, country, etc.).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2025-06-18+ | v2 |
No error recovery guidance. If site_url is invalid or user lacks permission, no hint on how to recover (e.g., 'Call gsc_list_sites first to find valid properties').