Loading ToolBench
MCP server that provides access to SE Ranking's Data API and Project API for SEO data analysis, including backlinks, keywords, domain analysis, website audits, and AI search insights
SE Ranking server has well-structured tool definitions with complete input schemas and consistent naming patterns. All 8 tools follow verb_noun convention (get*, list*) and include parameter descriptions. However, tool descriptions are generic API documentation rather than LLM-optimized guidance. Output schemas are not documented, LLMs cannot predict response structure. Error handling is minimal. Tool descriptions average ~120 chars but lack context on WHEN to use each tool vs. alternatives, and lack dependency hints. No batch variants despite tools accepting arrays (getTotalRefDomainsCount). Security: API tokens properly injected server-side via environment variables.
Data Tool: Fetch site pages that have backlinks, with sorting and limit controls (v1/backlinks/indexed-pages)
Data Tool: Retrieves a list of referring domains pointing to the specified target, with options for sorting and limiting results.
Data Tool: Returns information about the distribution of Domain InLink Rank (Domain Authority) of all the domains that reference a specific target.
Data Tool: Returns information about the domain InLink Rank (Domain Authority) of the target page's root domain.
Data Tool: Returns historical Domain InLink Rank (Domain Authority) values for a target domain. The target is always resolved to its PLD (pay-level domain) regardless of whether a root domain, host, or URL is provided.
Data Tool: Returns the number of referring domains, at least one backlink from which was newly found or lost in the specified date range, broken down by day.
Output schemas not documented. LLMs cannot predict response structure, field names, or types. Downstream tool chaining requires guesswork.
Tool descriptions are generic API documentation (50-60 chars) lacking LLM-optimized guidance. Missing WHEN to use each tool, dependencies, and distinctions from similar tools (e.g., getBacklinksIndexedPages vs getBacklinksRefDomains).
No error recovery guidance. Tools return API errors without actionable next steps. E.g., invalid target format should suggest 'Use domain, host, or URL format' rather than raw API error.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | <=2025-11-25 | v2 |
Data Tool: Returns the number of unique domains linking to a target. Supports batch requests.
Data Tool: Returns a list of referring domains, at least one backlink from which was (newly) found or lost in the specified date range for the specified target.
Date parameters (date_from, date_to) lack format validation hints in descriptions. Should state 'YYYY-MM-DD format required' explicitly to prevent LLM hallucination of invalid formats.
No batch operation guidance. getTotalRefDomainsCount accepts array input but no documentation on batch size limits, partial failure handling, or response structure for batch requests.