AgentSEO MCP server defines 11 SEO-focused tools with consistent naming (verb_noun pattern: agentseo_*) and complete input schemas. All tools have descriptions (avg ~80 chars) and typed parameters with enums where appropriate. However, output schemas are entirely undocumented, no response structure is visible in the source. Parameter descriptions are minimal (often single phrases like 'The search query') and lack actionable constraints. Error handling is absent from tool definitions. The server follows basic MCP patterns but lacks production-grade polish: no guidance on when to use similar tools (e.g., agentseo_social_listen vs agentseo_web_mentions are identical), no recovery hints, and no documentation of API dependencies or rate limits.

• Document output schemas for all 11 tools. Include field names, types, and whether results are paginated. Example: 'Returns array of {url, title, snippet, domain} objects, paginated with next_cursor.'
• Expand parameter descriptions to 50-100 chars with actionable constraints. E.g., 'Geographic location (country name or city, e.g., "United States" or "New York"). Affects SERP results and local rankings.'
• Merge agentseo_social_listen and agentseo_web_mentions into a single tool, or document the functional difference in each description.
• Add error handling guidance to tool descriptions. E.g., 'If domain not found, returns empty results. Try agentseo_search to verify the domain exists first.'
• Document rate limits, API dependencies, and async behavior. The 'sync' parameter suggests async is available, explain when to use each and what polling looks like.