Skip to main content
Glama
EuroScrape

EuroScrape MCP server

Official
by EuroScrape
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

No-Website Leads: New Businesses Without a Website (US, UK, FR)

find_new_companies_without_website
Read-only

Find newly registered companies without a website in the UK, France, and five US states for web design or digital service outreach.

Instructions

Companies registered in the last days in the UK, France and five US states (Texas, New York, Colorado, Connecticut, Oregon) that have no website yet, from official registers, with the creation date of their domain name when one exists. Companies only, no director names. Pay per result on your Apify account: run start $0.003, no-website lead $0.005, new company with a website, or undecided $0.002.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputNo"Without a website" returns every company with no site of its own, and tells whether a domain name at its name exists and when it was created. "Domain just bought" keeps only the companies whose domain was created around their registration and shows no site yet: they are about to need one. "All" also returns the companies that already have a website, with emails and phones found on it.
maxItemsNoThe run stops when this many leads are saved. Default here: 25.
usStatesNoStates to read. Leave empty for the five of them. Texas publishes a new company about ten days after its charter date, and Oregon updates its list once a week: set "Registered in the last N days" to 21 or more to get all of them.
countriesNoRegisters to read. With several, leads are taken from each country in turn. United States: five states publish their new companies as open data (New York, Texas, Colorado, Connecticut, Oregon).
ukLocationsNoRegistered office contains one of these, e.g. "Leeds", "Manchester", "SW1". Leave empty for the whole UK.
usLocationsNoCity names, e.g. "Denver", "Hartford", "Boulder". For New York, county names work too: "Kings" (Brooklyn), "Queens", "Albany". Leave empty for the whole state.
frDepartmentsNoDepartment numbers, e.g. "75", "69", "13", "2A". Leave empty for all of France.
activityKeywordsNoKeep companies whose activity or name contains one of these, e.g. "restaurant", "plumbing", "coiffure", "beauty salon". Several words in one entry must all be present. UK activities are the official SIC descriptions (in English); French activities are written in French; in the US only Connecticut publishes an activity, so the name is what counts for New York, Colorado, Texas and Oregon. Leave empty for every activity.
registeredInLastDaysNoUK and US: registration date. France: date of the official notice, published a few days after the registration. The most recent companies come first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely extra context beyond the structured fields: official-register provenance, an explicit exclusion (no director names), a domain-creation-date signal, and per-result pricing tiers, which functions like a rate/cost disclosure.

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 what is returned before the pricing detail, and every clause carries information (geography, source, exclusions, cost). It is dense but not padded; only the pricing enumeration at the end is slightly heavy for a description field.

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 9-parameter, zero-required, filter-style tool with no output schema, the description supplies what the schema cannot: data provenance, geographic coverage caveats, the meaning of the lead signals, and cost per result. Nothing essential for correct invocation 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 enum for 'output' is documented in the schema itself, so the baseline is 3. The description only restates the scope (US/UK/FR, official registers, companies only) and adds pricing tied to result types, without meaningful parameter syntax or format detail beyond the schema.

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 precise verb and resource (find newly registered companies without a website) plus exact scope: UK, France, and five named US states, sourced from official registers. This is readily distinguishable from siblings like search_uk_companies or search_french_companies because the no-website filter and recency window are named explicitly.

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

Usage Guidelines3/5

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

The description conveys the context in which this tool applies (new companies lacking a website) but never routes the agent between this and the overlapping sibling tools (search_uk_companies, search_french_companies), nor states when not to use it. Usage is implied rather than explicit.

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

Deploy Server

Other Tools