Explore tools Use a company’s domain to assemble account context in your assistant, and distinguish that record from LinkedIn profile access.
Company-domain research only. No LinkedIn profile viewer, post publishing or contact verification.
Begin with the organization’s own website domain. A product brand, subsidiary and parent company can have different records. The research tool accepts a domain, not a LinkedIn profile URL. Verify the returned name before attaching the result to an account.
Use the MCP connection instructions for your client, then inspect the tools the server actually exposes. Ask for company research on a specific domain and review the request before running it. An installed connection does not mean every upstream dataset is available.
A company record may include a description, industry, location, founding year, employee estimate or a LinkedIn company URL. A returned link is a source to inspect, not proof that The Spawn fetched that LinkedIn page or verified its current contents.
LinkedIn’s own Organization Lookup API documents organization retrieval within its API access model. Reading company information, viewing people, managing an organization and publishing posts are different actions. This workflow promises none of the latter actions.
Compare the company profile with its current website and your existing account notes. Write a question that the evidence leaves open. Avoid converting a company category or employee estimate into a claim that a particular person needs your product.
Keep the domain, retrieved date, available fields and missing information together. If the business identity does not match, stop and correct it. For repeated account research, use the company API contract; batch enrichment and LinkedIn-native access are separate capabilities.
Reviewed 2026-09-14