Loading ToolBench
Google Search Console in Claude, Cursor and other MCP clients. Local, read-only, free.
SearchLink Lite demonstrates solid tool design with clear naming, comprehensive descriptions, and well-structured schemas. All 7 tools follow verb_noun conventions (list_sites, site_overview, search_performance, page_check, algorithm_updates, inspect_url, list_sitemaps). Descriptions are detailed (100-250 chars typical) and explain WHAT, WHEN, and WHY. Input schemas use proper JSON Schema with types, enums, min/max constraints, and descriptions for all parameters. However, output schemas are not formally documented in the code, responses are constructed as markdown tables and text, making it difficult for LLMs to parse structured data reliably. Error handling is present but minimal (e.g., 'not in your Search Console' error), lacking recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being read-only.
Google's public ranking update history. Used to explain a traffic change. Returns a list of recent Google algorithm updates with their start and end dates.
Inspect a URL in Google Search Console: indexing status, mobile usability, rich results, and more. Returns detailed inspection results from Google's index.
Lists all sitemaps submitted to a Search Console property, with their status, errors, warnings, and submission history.
Lists every Search Console property the credentials can read, with the access level of each. Call this first when the user has not named a site, or when another tool says a site was not found. Read-only. Returns a table of property URLs and permissions.
Reads one page the way a search engine does: title, description, canonical, robots rules, headings and structured data. Plain fetch plus HTMLRewriter, so there is nothing to pay for. Returns a detailed analysis of on-page SEO factors.
Custom Search Console report when site_overview is not specific enough: group by query, page, country, device or date (up to two at once), filter by query or page text, sort, and optionally add the change against the previous period. Returns a table with clicks, impressions, CTR and position per row. Read-only.
Output schemas not formally documented. Tools return markdown tables and free-text responses instead of structured JSON. LLMs cannot reliably parse or chain results.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). All tools are read-only but this is not declared in the schema, forcing LLMs to infer safety from descriptions.
Error handling lacks recovery guidance. 'not in your Search Console' error does not suggest next steps (e.g., 'Call list_sites() to see available properties').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
The first tool to call for any question about how a site is doing on Google. Returns total clicks, impressions, CTR and average position for the period against the period before (totals match the Search Console UI), the pages that gained and lost the most clicks, and up to 3 plain-language things to do now. For custom breakdowns use search_performance instead. Read-only.
page_check and inspect_url descriptions are vague about what 'detailed analysis' and 'detailed inspection results' contain. LLMs cannot predict output structure.
No pagination or limit parameters on list_sites and list_sitemaps. If a user has hundreds of sites or sitemaps, responses could exceed context limits.