Workflow tools
Use these first when your request maps to a GTM job rather than one API call:| Tool | Use it for |
|---|---|
build_prospect_list | Search target companies, find relevant people, and optionally enrich contacts. |
find_people_at_target_accounts | Find contacts at a known list of company domains or names. |
enrich_prospect_list | Enrich a batch of known prospects with requested contact fields or signals. |
research_company | Crawl a company site, search recent web results, and run structured deep research. |
research_person | Build a structured research dossier for a person or prospect. |
monitor_topic | Create monitors for a topic, company, profile, or post, and optionally run them immediately. |
analyze_social_profile | Fetch and summarize bounded public Instagram or TikTok profile data. |
scrape_and_extract | Scrape one URL and optionally extract structured data with deep research. |
API tools
Use these when you want direct control over a specific public API endpoint:| Area | Tools |
|---|---|
| Companies and people | search_companies, search_people |
| Enrichment | enrich_contact, enrich_contacts, get_enrichment |
| Research and operations | start_deep_research, get_operation |
| Search | submit_search, get_search_result, list_searches |
| Web scraping | search_web, crawl_website, scrape_web_page |
| Social scraping | get_instagram_profile, list_instagram_posts, get_instagram_post, list_instagram_post_comments, list_instagram_followers, list_instagram_following, get_tiktok_profile |
| Monitors | create_monitor, list_monitors, get_monitor, update_monitor, delete_monitor, run_monitor_now, list_monitor_events |
Example prompts
Async results
Many The Hog API calls run asynchronously. MCP tools may return an operation ID, poll URL, child operation IDs, warnings, and partial step results. If a tool returns an operation ID instead of final data, ask your client to callget_operation with that ID.
Deep-research-bearing tools (research_company, research_person, scrape_and_extract, start_deep_research) are async-first: because deep research runs for minutes, they return an operation ID immediately (status queued) rather than blocking. Poll get_operation until the status is completed to fetch the result. You may set waitForResult: true to wait inline, but the wait is capped at ~50s (below the ~60s MCP client/gateway ceiling); if it does not finish in time you still receive the operation ID to poll. Re-attaching with get_operation does not consume additional credits — do not re-issue the call to retry.