webdatatools-leads-mcp

company_360

Turn company domains into rich profiles with contacts, tech stack, DNS/email security, TLS headers, SEO, hiring signals, and company facts in one row per domain.

Instructions

Company 360 turns a domain into one rich profile row: contacts, tech stack, DNS/e-mail security, TLS/security headers, on-page SEO, hiring signals and company facts (HQ, employees, revenue, founders) merged from our own scraper suite. Billed to your own Apify account: ~$0.05 per company (Apify free-plan price, lower on paid plans).

Input Schema

TableJSON Schema

Name	Required	Description
`domains`	Yes	Domains — Enter the company domains to profile, one row is returned per domain, e.g. apify.com. Full URLs and www. prefixes are accepted and stripped automatically, so you can paste a list straight out of your CRM. Example: ["apify.com"].
`includeSeo`	No	Include SEO audit — Call our On-Page SEO Audit Actor for the home page's 0-100 SEO score and a list of issues found.
`includeHiring`	No	Include hiring signals — Call our Hiring Signals Actor for open job counts and hiring velocity. Only returns data when the domain's ATS job board could be found under its own name (e.g. a Greenhouse/Lever/Ashby board named after the company) - most domains will not match and get a warning instead, not an error.
`includeContacts`	No	Include contacts — Fetch the homepage (and a common contact-page guess) for e-mail addresses, phone numbers and social-profile links.
`includeTechStack`	No	Include tech stack — Call our Tech Stack Detector Actor for CMS, e-commerce platform, analytics, ad pixels, chat widget and payment providers.
`includeCompanyFacts`	No	Include company facts — Call our Wikidata Entity Enrichment Actor for headquarters, employee count, revenue, founders, founding date and Crunchbase/LinkedIn IDs. Works best for companies with a Wikidata entry.
`includeEmailSecurity`	No	Include DNS & e-mail security — Look up SPF/DMARC policy, mail provider, DNS provider, registrar and domain age directly (no sub-Actor call).
`includeSecurityAudit`	No	Include security audit — Call our Domain Security Audit Actor for TLS certificate validity/expiry and a 0-100 security grade based on HTTP security headers.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden and adds meaningful context: billing is charged to the user's own Apify account at roughly $0.05 per company, most sub-data comes from named scraper Actors, and the hiring-signals component returns warnings rather than errors when no ATS board is found. It still does not state authentication requirements or explicitly confirm read-only behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core purpose and followed by pricing. The long first sentence is an efficient enumeration of included data categories, and no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 8-parameter aggregate with no annotations and no output schema, the description explains the row-level output, the main data categories, the one-row-per-domain behavior, and the cost model. It is nearly complete, though it omits explicit auth requirements and alternative-tool routing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in the input schema, including the domains format and each include flag. The description adds no parameter-level syntax or constraints beyond what the schema provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it turns a domain into a rich company profile row. It enumerates the merged data categories (contacts, tech stack, DNS/e-mail security, TLS, SEO, hiring, company facts) and makes clear this is an aggregate rather than a single-purpose sibling like hiring_signals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but gives no explicit when-to-use, when-not-to-use, or alternative guidance. It does not say whether to prefer this aggregate over individual sibling tools such as hiring_signals or wikidata_entity_enrichment when only one data category is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

company_360

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools