Skip to main content
Glama

Create a lead search

create_search

Creates a new lead search («поиск лидов») from the onboarding answers and starts compiling its requirements (~1-2 minutes; nothing is charged in credits, but it spends the onboarding's brief if no assistant did). Then poll get_search every 20-30 s until status is ready, review the spec with the user (get_search detail=spec), and only then quote and run it. company and icp are required. [REST: POST /api/tasks]

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": {
      "company": "<company>",
      "icp": "<icp>"
    },
    "name": "create_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
icpYesWhom to find: the customer profile (step 3).
goalNoWhat the outreach should achieve (step 2).
companyYesWhat the user's company does (step 1).
languageNoLanguage of the outreach messages (default english).
source_taskNoThe earlier onboarding this one was filled from (get_onboarding_prefill).
exclude_urlsNoLinkedIn profile links of people to leave out.
exclude_scopeNoFrom those searches: everyone analysed (all) or only leads.
exclude_tasksNoEarlier searches whose people to leave out.
onboarding_idNoThe onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the same new search.
exclude_companiesNoAlso leave out the companies of those people.
exclude_company_urlsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "english",
      -  "russian"
      -]New value: +[
      +  "english",
      +  "russian",
      +  "spanish",
      +  "french",
      +  "german",
      +  "portuguese",
      +  "italian",
      +  "chinese",
      +  "japanese",
      +  "korean",
      +  "arabic",
      +  "hindi"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses timing (~1-2 minutes), credit cost (nothing charged), a side effect that consumed onboarding brief is spent, and the fact that onboarding_id comes back on the first call. These are non-obvious operational facts an agent would otherwise learn by failure.

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 the action and timing, then the workflow, then the REST path. Dense but every clause carries information; the parenthetical cost/consumption note is slightly compressed and would read better as its own short sentence.

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 an 11-parameter creation tool with no output schema, the description still covers duration, cost model, the returned onboarding_id handshake, and the full downstream sequence. An agent knows what to expect immediately after calling and what to do next.

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 91%, so the schema already documents company, icp, goal, onboarding_id, exclusions and language in detail. The description only restates that company and icp are required, which the schema's required array already declares, so it adds little meaning of its own. Baseline 3 is appropriate.

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+resource ('Creates a new lead search') and adds what happens next ('starts compiling its requirements'), which separates it from get_search, quote_search and run_search. An agent can tell this is the entry point of the pipeline without opening the schema.

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 an explicit ordered workflow: create, then poll get_search every 20-30 s until status is `ready`, then review the spec with detail=spec, then quote and run. The sequencing constraint ('only then') tells the agent what not to do, which is exactly the guidance a multi-step pipeline needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources