MisarReach MCP Server

sync_lead_list

DestructiveIdempotent

Import a managed lead list into local lead records so listing, enrichment, and campaign tools can access its contacts; re-syncing refreshes records without duplicates.

Instructions

Import a managed lead list into local lead records so the rest of these tools can work with it.

Run it after create_lead_list, or on any existing list from list_lead_lists, to pull its contacts in. Until a list is synced its contacts are invisible to list_leads, enrich_lead and send_to_campaign.

Writes local lead records, and OVERWRITES any saved lead with the same email address: its name, role, company, score and verification status are replaced and it is detached from its search job. Re-syncing the same list refreshes rather than duplicating. Requires an API key. Costs no credits; enrichment and verification are billed separately.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listId": "<listId>"
    },
    "name": "sync_lead_list"
  }
}

Input Schema

Name	Required	Description	Default
`listId`	Yes	Lead list ID from list_lead_lists (integer as string)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv5.2.1Oct 18, 2026

changedInput schema / properties / listId / description

Previous value: -"Hunter.io list ID (integer as string)"New value: +"Lead list ID from list_lead_lists (integer as string)"

First observedv2.0.0Aug 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructive=true, idempotent=true, and readOnly=false, and the description reinforces and expands this: it names exactly which fields get overwritten (name, role, company, score, verification status), notes detachment from search job, clarifies re-sync refreshes rather than duplicates, and adds auth (API key) and cost (no credits) context. This is well beyond what the annotations convey.

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

Conciseness4/5

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

Purpose is front-loaded and each sentence carries needed information. Slightly long, but the overwrite warning and billing note are high-value and not padding.

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

Completeness5/5

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

For a one-param mutation with no output schema, everything an agent needs is present: prerequisites, side effects, overwrite semantics, idempotency behavior, auth and cost. Nothing material is missing.

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% and the single listId parameter is documented as coming from list_lead_lists. The description corroborates the source but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: importing/syncing a managed lead list into local lead records. It clearly distinguishes itself from siblings by naming create_lead_list and list_lead_lists as its inputs, so an agent immediately knows this is the ingestion step.

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

Usage Guidelines5/5

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

Gives explicit when-to-use conditions ('Run it after create_lead_list, or on any existing list from list_lead_lists') and consequences of not doing it (contacts invisible to list_leads, enrich_lead, send_to_campaign). No inference required.

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