Hosted Enrichment Crawlers MCP server, with each action switched on or off per account.
Scored across 4 tools
execute_action and query_data have essentially identical descriptions, both being 'Step 3 (FINAL)' with the same prerequisites and the same list of crawler actions, so an agent cannot reliably choose between them. query_contexts and prompts_menu are more distinguishable, but the core execution pair creates a serious selection hazard.
All names use snake_case, which is consistent at the surface level, but the patterns differ: query_contexts/query_data are verb_noun pairs while execute_action is a vague verb and prompts_menu is noun-based. The near-synonymous 'execute' vs 'query' verbs give no naming signal about which tool actually runs enrichment.
Four tools is on the thin side for a workflow that spans workspace discovery, action schema lookup, execution, and a prompt catalog. Effectively there are only three distinct capabilities because two tools duplicate one another, making the set feel slightly under-scoped.
The lifecycle of discover-actions, inspect-schema, then execute is covered, and prompt listing includes both public and custom detail lookups. However, having two parallel execution entry points with no stated difference means coverage is duplicated rather than extended, and there is no prompt write/manage capability.
Execute Company Enrichment actions (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id AND available_actions
request='actions_details' with actions=['xxxxxx'] - Get detailed body structure (replace xxxxxx with actions from available_actions)
Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.
Common actions:
discovery-crawler: Find company from email domain
profile-crawler: Get company profile details
metrics-crawler: Get company metrics
funding-crawler: Get funding data
tech-stack-crawler: Detect tech stack
leadership-crawler: Get leadership info
Inputs: body (required). Returns: object
Helper for planning InsightfulPipe Company Enrichment queries.
Step 1: request='accounts' – Retrieve workspace_id AND available_actions (all enrichment actions you can use).
Step 2: request='actions_details' with actions=['xxxxxx'] – REQUIRED before querying. Replace xxxxxx with actions from available_actions to get the exact request body, required fields, and parameters for each action.
Optional: request='available_actions' – Standalone call to list all available actions (already included in accounts response).
Inputs: request (required), actions, platform, workspace_id. Returns: object
Execute Company Enrichment queries (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id AND available_actions
request='actions_details' with actions=['xxxxxx'] - Get detailed body structure (replace xxxxxx with actions from available_actions)
Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.
Common actions:
discovery-crawler: Find company from email domain
profile-crawler: Get company profile details
metrics-crawler: Get company metrics
funding-crawler: Get funding data
tech-stack-crawler: Detect tech stack
leadership-crawler: Get leadership info
Inputs: body (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Hosted Google Search Console MCP server, with each action switched on or off per account.
Hosted Bing Webmaster Tools MCP server, with each action switched on or off per account.
Hosted Web Crawler MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Hosted Microsoft Ads MCP server, with each action switched on or off per account.
Add one secure layer between your agents and this server.