Loading ToolBench
MCP server for Domain to LinkedIn URL Resolver. Resolves a company domain or name to its LinkedIn company URL with confidence scoring and firmographics via Apify. Clay-ready output.
Single tool with strong naming (verb_noun: resolve_linkedin_url), comprehensive description (194 chars, well-structured), and complete Zod schema with all parameters typed and described. Tool annotations present (readOnlyHint, idempotentHint, destructiveHint). Output schema not explicitly documented, response is raw JSON from Apify without field-level documentation. Error handling is good (specific HTTP status codes with recovery guidance). No critical gaps, but output schema documentation would elevate to 80+.
Resolve a company domain or name to its LinkedIn company URL. Returns the LinkedIn URL with a confidence score, plus firmographics such as employee count, industry, and headquarters, and social links, as a flat, Clay-ready JSON row. Provide at least one of company_domain or company_name. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
Output schema not documented. Tool returns raw JSON from Apify API without explicit field definitions. LLMs cannot plan downstream operations or extract specific fields reliably.
Enum parameters use string values ('false', 'true') instead of boolean type. While Clay-compatible, this is non-standard for MCP and forces LLMs to reason about string literals rather than native types.
No pagination or result limiting documented. If Apify returns large datasets (e.g., multiple company matches), response could exceed context window. Tool description should state result limits.
APIFY_TOKEN exposed as environment variable without explicit secret injection pattern documentation. While not a parameter, the README should emphasize secure token handling and vault integration for production.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | B | 70 | 2026-07-28+ | v2 |