← ZoomInfoCONTENT HISTORY

Update to ZoomInfo

Snapshot Sep 30, 2026 · 22:44 UTC · version 6.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "enrich-contact",
  "description": "Look up a person's full professional profile. Provide a name and company, email address, phone number, or ZoomInfo person ID. Returns title, department, contact details, accuracy score, and company info.",
  "included_files": [],
  "skill_md_contents": "---\nname: enrich-contact\ndescription: Look up a person's full professional profile. Provide a name and company, email address, phone number, or ZoomInfo person ID. Returns title, department, contact details, accuracy score, and company info.\n---\n\n# Enrich Contact\n\nLook up a single contact's full profile in ZoomInfo.\n\n## Input\n\nThe user will provide via `$ARGUMENTS` one of:\n- An email address (e.g., `jane@acme.com`)\n- A name and company (e.g., `Jane Smith at Acme Corp`)\n- A phone number\n- A LinkedIn URL\n- A ZoomInfo person ID\n\n## Workflow\n\n1. **Lookup metadata first** — before calling any other MCP tool, use `lookup` to load reference data for any fields relevant to the request. Use the returned `id` values (not display names) in all subsequent API calls. This ensures accurate parameter resolution, especially if a fallback search is needed.\n\n2. **Identify the best match key** from the user's input:\n   - Email → use `email` parameter\n   - Name + company → use `firstName`, `lastName`, `companyName`\n   - Full name + company → use `fullName`, `companyName`\n   - Phone → use `phone`\n   - LinkedIn URL → use `externalURL`\n   - Person ID → use `personId`\n\n3. **Enrich the contact** using `enrich_contacts` with the identified parameters.\n\n4. **If no match**, try a fallback:\n   - If name + company failed, try `search_contacts` with `jobTitle` or `companyName` variations — use lookup `id` values for any filters\n   - Suggest alternative spellings or company names\n\n## Output Format\n\n**[Full Name]** — [Title] at [Company]\n\n| Field | Value |\n|-------|-------|\n| Department | |\n| Management Level | |\n| Email | |\n| Direct Phone | |\n| Mobile Phone | |\n| Accuracy Score | |\n| Location | |\n| Company | |\n| Company Industry | |\n| Company Size | |\n| LinkedIn | |\n| Last Updated | |\n| ZoomInfo Person ID | |\n\nIf any fields are unavailable, omit them rather than showing blanks. Note the accuracy score prominently — anything below 80 deserves a flag.\n"
}

SHA-256: aef02fdc74afb22053e37546861c0e86e4b23479337dcc2acd8ad48e148901ce