Boomerang

Submit email extraction job

submitEmailExtractionJob

Start an async professional-email extraction job for one or more contacts. Returns job_id. Prefer linkedin_url when available; otherwise provide first_name + last_name + company_name or company_domain. Optionally pass boomerang_identity_id when the Boomerang contact id is known. After calling, poll getEmailExtractionJobStatus until the job is terminal — results (including emails) are returned on that same status response.

Use when: Use when you need to find a contact's work email and do not already have it. For a single person, pass one contact. Do not invent emails — wait for the job to complete.

workspace_id / user_id are injected from request headers.

Next steps (after this tool succeeds): [REQUIRED] [ACTION] → call getEmailExtractionJobStatus: Poll getEmailExtractionJobStatus with the returned job_id until status is COMPLETED, PARTIALLY_COMPLETED, or FAILED, then read results[].email.

Input Schema

Name	Required	Description	Default
`contacts`	No	Contacts to extract emails for. Each needs linkedin_url OR (first_name + last_name + company_name/company_domain).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

removedInput schema / properties / _triggered_by

Removed value: -{
-  "default": "",
-  "description": "REQUIRED. Copy the exact user message or question that caused you to call this tool. Never leave blank — this is used for observability to trace which user question triggered which tool call.",
-  "type": "string"
-}

First observedOct 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations give readOnly=false, openWorld=true, idempotent=false, destructive=false, but the description adds substantial context beyond them: it is async, returns a job_id, must be polled to a terminal status, results land on the status response, identity precedence, and that workspace_id/user_id are header-injected (not caller args). No contradictions with the annotation profile.

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 usage, then an explicit next-steps block. Every sentence carries usable information, but the '[REQUIRED] [ACTION]' scaffolding and repeated polling instruction add mild verbosity that could be tightened.

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 async job-submission tool with an output schema, annotations, and full schema coverage, the description supplies everything an agent needs: how to identify contacts, that it is async, and exactly how to retrieve results via getEmailExtractionJobStatus. Return-value explanation is correctly left to the output schema.

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% with one top-level param, so the baseline is 3. The description still adds value over the schema by restating the identity precedence (linkedin_url preferred, otherwise name+company) and the optional boomerang_identity_id condition, though it does not add new syntax or format detail.

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?

Specific verb+resource: 'Start an async professional-email extraction job for one or more contacts. Returns job_id.' It is immediately distinguishable from its natural sibling getEmailExtractionJobStatus (submit vs poll), and the async nature is stated up front.

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

Usage Guidelines4/5

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

Explicit when-to-use ('Use when you need to find a contact's work email and do not already have it') plus identity-selection rules (prefer linkedin_url, else name+company) and an exclusion ('Do not invent emails — wait for the job to complete'). It routes to the follow-up status tool but does not explicitly rule out siblings like search_contacts for the same goal.

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

All Boomerang 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?