Funkel AI

import_search_leads_to_list

Destructive

Import lead rows from a prior search_external_leads session into a lead list. Two-phase: first call returns a confirmation token + preview; the user reviews an inline card and confirms; second call with confirmation_token commits. provider_ids omitted means import every lead in the search session. Supply list_id for an existing list, or list_name to create a new list during the confirmed commit. After a committed result returns list_id, use that exact list_id when creating a campaign from the imported search leads. Over MCP: call this tool once, without confirmation_token. It runs right away and returns the result.

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": {
      "session_id": "<session_id>"
    },
    "name": "import_search_leads_to_list"
  }
}

Input Schema

Name	Required	Description
`list_id`	No	Existing lead list id to import into (UUID format, e.g. 550e8400-e29b-41d4-a716-446655440000)
`list_name`	No	Name for a new list to create during the confirmed import when list_id is omitted
`session_id`	Yes	Lead search session id returned by search_external_leads (UUID format, e.g. 550e8400-e29b-41d4-a716-446655440000)
`provider_ids`	No	Optional selected provider ids from the search result. Omit to import all search results.
`confirmation_token`	No	Phase-2 token (omit on phase-1)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent; the description adds valuable flow detail (two-phase confirm, inline card preview, phase-1 vs phase-2 token, MCP single-call behavior) that the annotations don't convey. It stops short of saying what happens to previously imported rows or how duplicates are handled, so it's strong but not exhaustive.

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?

Front-loaded with purpose, then the two-phase flow, then parameter decisions, ending with the MCP-specific shortcut. Sentences are dense and purposeful, though the final MCP paragraph slightly re-frames the earlier two-phase narrative and reads as a mild afterthought.

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 non-idempotent, destructive mutation with no output schema, the description explains the return shape (confirmation token, preview, committed list_id) and the MCP invocation path, leaving no ambiguity about how to call it correctly. Nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: provider_ids omitted means import all, and list_id vs list_name is a mutually exclusive create-vs-use choice. That mutual-exclusivity semantics is not stated in the schema itself.

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 (import), the resource (lead rows), the source (a prior search_external_leads session), and the destination (a lead list). This clearly distinguishes it from siblings like search_external_leads (which finds leads) and create_list (which only creates a list).

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?

Explicitly covers each decision point: omit provider_ids to import everything, use list_id for an existing list vs list_name to create one, and call once without confirmation_token over MCP. It also names search_external_leads as the required prior step and gives downstream guidance about reusing the returned list_id for campaign creation.

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

All Funkel AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?