Copy page

Remote MCP server

Tools, prompts, and resources

The remote MCP server has 28 tools, each of which uses your Tomba account. This page lists every tool with its parameters as the server validates them, followed by the prompts and resources. The local server differs in the ways listed under Local server differences.

Conventions

• Tool and parameter names are snake_case. Leave out optional parameters rather than sending null.
• The server checks arguments against each tool's input schema before it calls the API. Invalid arguments return a tool error; see Errors.
• The parameter tables use these formats:
  • Domain: a domain name such as stripe.com, without a scheme or path. It must match ^[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$.
  • Country: two uppercase letters, as in ISO 3166-1 alpha-2, such as US.
  • Phone: an optional + and 2 to 15 digits, the first of which isn't 0, with no spaces, such as +14155552671.
  • Public URL: an http or https URL whose host isn't localhost or a private IPv4 address.
• Each tool returns the API response as structuredContent in the form {"data": <response>}, and the same JSON as text. The response fields are those of the API endpoint listed for the tool.
• A tool call is billed as the API request it makes; see Credit costs. With OAuth, a tool needs the scope of its endpoint; see OAuth 2.0.
• create_flag and create_lead change data in your account. Every other tool carries the annotation readOnlyHint: true, and all tools carry openWorldHint: true. Clients that read annotations, such as ChatGPT, ask you to confirm the two write tools.
• Where a tool accepts webhook_url, the API also sends the result to that URL; see Per-request callbacks.

A tools/call request looks like this. limit is a string, not a number:

Code
{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
        "name": "domain_search",
        "arguments": { "domain": "stripe.com", "limit": "20" }
    }
}

Find email addresses

domain_search

Finds the email addresses Tomba has for a company, by domain or company name. Calls GET /v1/domain-search.

email_finder

Finds a person's email address from their name and company. Calls GET /v1/email-finder.

author_finder

Finds the email address of an article's author. Calls GET /v1/author-finder.

linkedin_finder

Finds the email address that belongs to a LinkedIn profile. Calls GET /v1/linkedin.

email_count

Counts the email addresses Tomba has for a domain. Calls GET /v1/email-count.

email_format

Returns the patterns a domain uses to build email addresses. Calls GET /v1/email-format.

email_sources

Lists the web pages where Tomba found an email address. Calls GET /v1/email-sources.

Verify

email_verifier

Checks whether an email address can receive mail. Calls GET /v1/email-verifier. The status and result values are explained in Email verifier response.

domain_status

Checks whether a domain belongs to a webmail or disposable email provider. Calls GET /v1/domain-status.

Enrich

email_enrichment

Returns the person and company behind an email address. Calls GET /v1/enrich.

person_enrichment

Returns a person's profile from their email address. Calls GET /v1/people/find.

company_enrichment

Returns a company's profile from its domain. Calls GET /v1/companies/find.

combined_enrichment

Returns the person and company profiles for an email address in one call. Calls GET /v1/combined/find.

Phone numbers

phone_finder

Finds phone numbers from an email address, a domain, or a LinkedIn profile. Calls GET /v1/phone, which behaves like GET /v1/phone-finder.

phone_validator

Validates a phone number. Calls GET /v1/phone-validator.

Companies and domains

companies_search

Searches Tomba's company database with a text query and filters. Calls POST /v1/reveal/search.

filters accepts the keys location_country, location_city, location_state, industry, size, type, keywords, founded, technologies, similar, revenue, sic, and naics. Each key takes an object with include and exclude arrays of strings. The accepted values are described in the request body of Search companies.

Code
{
    "filters": {
        "location_country": { "include": ["US"] },
        "industry": { "include": ["Computer Software"] }
    },
    "page": 1
}

similar_finder

Finds companies similar to a domain. Calls GET /v1/similar.

technology_finder

Lists the technologies a website uses. Calls GET /v1/technology.

autocomplete

Suggests companies, with their domains and logos, for a partial company name. Calls GET /v1/domain-suggestions.

location

Counts a company's employees by country. Calls GET /v1/location.

Account

account_info

Returns your account details, plan, and usage. Calls GET /v1/me. It takes no parameters.

usage_info

Returns your API usage. Calls GET /v1/usage. It takes no parameters. It needs key authentication and fails when you signed in with OAuth.

list_keys

Lists the API keys of your workspace. Calls GET /v1/keys. It takes no parameters.

get_logs

Returns your recent API requests. Calls GET /v1/logs. It needs key authentication and fails when you signed in with OAuth.

Leads and flags

list_leads

Lists your leads. Calls GET /v1/leads.

create_lead

Adds a lead to one of your lead lists. This tool changes data. Calls POST /v1/leads.

list_flags

Lists the reports of incorrect data you've submitted, with their status. Calls GET /v1/flag.

create_flag

Reports incorrect data, such as an address that bounced. This tool changes data. Calls POST /v1/flag. Which reports earn a credit back is explained in Refunds for incorrect data.

Prompts

Prompts are message templates that start a multi-step task with the tools. Clients show them as commands or templates, and ask for the arguments. Arguments are text.

The server lists optional arguments that have a default value as required, so your client may ask for them. Arguments with a fixed set of values reject anything else, and the error lists the allowed values.

numberOfCompanies and quarterlyTarget are numbers in the server's schema, but clients send every prompt argument as text, and the server rejects text for them. Leave both empty; numberOfCompanies then defaults to 10.

Resource URIs

Local server differences

The local MCP server, @tomba-io/tomba-mcp-server, has the same 28 tools, under the same names. This section describes version 1.2.0.

Parameters that differ from the tables above:

• email_finder takes fullName, firstName, and lastName in camelCase. firstName and lastName accept only ASCII letters, spaces, hyphens, and apostrophes, up to 50 characters; use fullName for other names.
• email_finder, email_verifier, email_enrichment, and linkedin_finder list an enrichMobile parameter, which version 1.2.0 doesn't pass to the API, so it has no effect.
• domain_search accepts only the department values listed in its schema.
• phone_validator lists a country parameter, which isn't passed to the API.
• companies_search has no query parameter. Its schema marks filters as required, accepts no technologies filter, and limits industry, type, size, and revenue to the values listed in the schema.
• list_flags, list_leads, and get_logs default page to 1 and limit to 10.

The local server has these prompts:

And these resources. Reading one of the four with a {domain} or {email} part calls the API, and is billed like the matching tool: