The LeadMagic MCP server exposes 17 tools with solid naming conventions (verb_noun pattern consistently applied) and reasonable descriptions. However, there are significant gaps in parameter documentation, output schema definition, and error handling guidance. Tools are well-named and descriptions are present but lack the depth required for production-grade LLM reasoning. Parameters have type definitions but many lack detailed descriptions explaining constraints, formats, or dependencies. No output schemas are documented, making it impossible for LLMs to plan downstream tool calls. Error handling is minimal, no recovery guidance, no categorization (retryable vs fatal), and no actionable messages. The server is functional but falls short of patterns for tool composition, response shaping, and LLM-optimized documentation.

• Document output schemas for every tool. Include field names, types, and whether fields are always present or conditional. Example: 'get_credits returns {credits: number}; find_email returns {email: string, confidence: number, sources: string[]}.'
• Add detailed parameter descriptions explaining constraints and formats. For 'profile_url': 'LinkedIn profile URL (format: https://linkedin.com/in/[username] or https://linkedin.com/company/[company-name]). Required.' For 'domain': 'Company domain without protocol (e.g., example.com, not http://example.com).'
• For tools accepting alternative parameters (domain vs company_name), add explicit mutual exclusivity guidance: 'Provide either domain OR company_name, not both. If unsure, use company_name (slower but more flexible).'
• Implement pagination for multi-item results. Modify find_employees, find_jobs, find_role to include page/offset/limit parameters in the schema and return {items: [...], total: number, page: number, has_more: boolean}.
• Add error handling wrapper that categorizes LeadMagicClient exceptions: if API returns 429, respond with 'Rate limit exceeded. Retry after 60 seconds.'; if 404, respond with 'Email not found. Try validate_email to confirm deliverability.'; if 401, respond with 'API key invalid or expired.'
• Implement result limits with pagination. Cap find_employees, find_jobs, find_role to 20-50 results by default and document this in descriptions.
• Standardize response field naming across related tools. Ensure email-finding tools all return 'email' (not 'email_address'), company tools return 'domain' (not 'company_domain'), and profile tools return consistent 'profile_url' / 'user_id' / 'name' fields.