Skip to main content
Glama

Trucking Company Leads: New FMCSA Carriers, Email & Phone

trucking_company_leads
Read-only

Pull US and Canadian carrier, broker and freight-forwarder records from FMCSA data to find new registrations, filter by fleet, cargo or state, or enrich USDOT numbers.

Instructions

Pull US and Canadian motor carrier, broker and freight-forwarder records from official FMCSA data, with phone, email, officers, fleet size, drivers, cargo, operating authority and safety rating. It runs in three modes: new USDOT registrations, filtered search of the registry, or lookup by USDOT number. Unlike local_business_leads (any category from OpenStreetMap) or npi_provider_lists (healthcare registry), this is the authoritative FMCSA registry for transportation companies. Use when you need new-entrant carrier leads (insurance, factoring, ELD, dispatch, fuel cards), carriers by lane/state/fleet/cargo, or to enrich known DOT numbers. Do not use for shipment tracking, load boards or rates. Parameters: mode=new uses daysBack and sorts newest first; mode=search ignores daysBack and uses the filters plus activeOnly; mode=lookup uses only dotNumbers. powerUnits/drivers bounds, carrierClass=forHire and requireEmail/requirePhone are the strongest narrowers and filter before billing. Phone and email are what carriers file with FMCSA and may be personal or stale. Runs that match nothing are free. Returns per item: agentSummary, dotNumber, mcNumber, legalName, dbaName, status, addedDate, daysSinceAdded, officers, phone, cellPhone, email, street, city, state, zip, powerUnits, drivers, fleetBand, cargo, hazmat, operation, carrierClasses, entityTypes, safetyRating, lastFilingDate, saferUrl.

Behavior: read-only; runs the Apify Actor pandadad0214/trucking-company-leads (https://apify.com/pandadad0214/trucking-company-leads) on your own Apify account. Price: $0.002 per carrier returned. Runs that find nothing are not charged per result, and spending is capped per call by run_max_charge_usd (default $0.50). run_max_items (default 50) limits items returned and fills maxResults when you leave it unset, so it also limits what is billed; setting maxResults higher can bill more than is returned. Most calls finish in 5-15 s for a few inputs; large inputs or crawls can take minutes, so raise run_timeout_secs (max 300) or shrink the input after a timeout error. Returns JSON {actor, count, items}; long text output is trimmed to whole items, with all items in structuredContent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trucking_company_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoWhat to find. New carriers = fresh USDOT registrations (the classic trucking-leads list for insurance, factoring, ELD, dispatch and fuel cards). Search = any carrier matching your filters. Lookup = details for a list of USDOT numbers. Choices: new = New carriers (registered in the last N days); search = Search all carriers by filters; lookup = Look up USDOT numbers.new
cargoNoCargo hauled (any of). Optional. Keep carriers that haul at least one of these, e.g. refrigerated food, building materials, livestock.
citiesNoCities. Optional. Exact city names, e.g. Houston, Laredo.
statesNoStates / provinces. 2-letter codes of the physical address (TX, CA, FL, ON…). Empty = all states.
daysBackNoRegistered in the last (days). New-carriers mode: how far back to look. 7 = this week's new entrants.
operationNoOperation. Interstate carriers cross state lines and usually need MC authority. Choices: any = Any; A = Interstate; B = Intrastate hazmat; C = Intrastate non-hazmat.any
activeOnlyNoActive USDOT status only. On by default. Off includes inactive and pending registrations (search mode).
dotNumbersNoUSDOT numbers (lookup mode). Lookup mode: one USDOT number per line (up to 1,000).
entityTypeNoEntity type. Find brokers instead of carriers, for example. Choices: any = Any; C = Carrier; B = Broker; F = Freight forwarder; S = Shipper; I = Intermodal equipment provider.any
hazmatOnlyNoHazmat carriers only. Only carriers flagged as hazardous materials carriers.
maxDriversNoMax drivers. Optional.
maxResultsNoMaximum carriers. You pay per carrier returned, so this also caps the cost. Newest registrations first.
minDriversNoMin drivers. Optional.
zipPrefixesNoZIP code prefixes. Optional. ZIP codes or prefixes, e.g. 850 for Phoenix, 770 for Houston.
carrierClassNoCarrier class. For-hire carriers haul other people's freight (best for brokers, factoring and dispatch). Choices: any = Any; forHire = For-hire (authorized for hire); private = Private (hauls own goods); exempt = Exempt for-hire; passenger = Passenger.any
nameContainsNoName contains. Optional. Word in the legal or DBA name, e.g. logistics, express, transport.
requireEmailNoOnly carriers with an email. Skip records with no published email.
requirePhoneNoOnly carriers with a phone. Skip records with no published phone.
maxPowerUnitsNoMax power units. Optional. 1 = owner-operators only.
minPowerUnitsNoMin power units (trucks/tractors). Optional. 1 = owner-operators and up; 5 = small fleets and up.
run_max_itemsNoOptional. Most results to return from this call (default from PANDA_MAX_ITEMS, 50). Also limits how many results the Actor produces and charges for, unless you set its own max field.
run_timeout_secsNoOptional. Seconds to wait for results (default from PANDA_TIMEOUT_SECS, 120; max 300).
updatedWithinDaysNoFiled an update (MCS-150) in the last (days). Optional. Carriers that updated their FMCSA registration recently (active, reachable companies).
run_max_charge_usdNoOptional. Hard spending cap for this call in USD (default from PANDA_MAX_CHARGE_USD, 0.50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/openWorld annotations: per-carrier pricing, free runs when nothing matches, a hard spend cap via run_max_charge_usd, the run_max_items/maxResults billing interaction, typical 5-15s runtimes with timeout remediation, and a candid caveat that phone/email are self-filed and may be personal or stale. Minor deduction because the timeout/charge semantics are restated rather than resolved in one place (it is unclear whether run_timeout_secs truncates results or errors).

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?

Long but front-loaded: purpose, differentiation, exclusions, then a parameter-behavior paragraph and a field list, with no filler. Some sentences duplicate schema text (run_max_charge_usd, run_timeout_secs defaults) and the 25-field return list is dense, but for a 24-parameter tool the density is earned.

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?

With no output schema, the description supplies the full item shape (agentSummary, dotNumber, officers, safetyRating, fleetBand, etc.) plus the wrapper {actor, count, items}. It covers cost, latency, error remediation, and data-quality caveats, so nothing material to invoking this correctly 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 already 100%, so the baseline is 3; the description earns above that by explaining cross-parameter coupling the schema cannot express - mode=new consumes daysBack and sorts newest first, mode=search ignores daysBack and applies activeOnly, mode=lookup uses only dotNumbers. It also ranks the highest-signal narrowers (powerUnits/drivers bounds, carrierClass=forHire, requireEmail/requirePhone) and flags the run_max_items vs maxResults billing trap.

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?

Opens with a specific verb and resource ('Pull US and Canadian motor carrier, broker and freight-forwarder records from official FMCSA data') and enumerates the returned fields. It explicitly distinguishes itself from two named siblings, local_business_leads and npi_provider_lists, so an agent can route correctly without opening a 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?

Provides concrete use cases (new-entrant carrier leads for insurance/factoring/ELD/dispatch, carriers by lane/state/fleet/cargo, DOT enrichment) and an explicit exclusion ('Do not use for shipment tracking, load boards or rates'). It also states which mode corresponds to which intent.

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