Skip to main content
Glama

Texas New Business Leads: New Franchise Taxpayers

texas_new_business_leads
Read-only

Find newly formed Texas LLCs and corporations by city, ZIP, county, or date using state franchise-tax data, with addresses, status, organization type, and SOS numbers.

Instructions

List new Texas businesses from the Texas Comptroller's active franchise taxpayer open data, matched on Secretary of State charter date or franchise-tax responsibility date, with address, county, organization type, SOS file number and status. Unlike florida_new_business_leads (Sunbiz filings with officers) and local_business_leads (OpenStreetMap shops), this is new Texas LLCs and corporations from state tax data; officers are not included. Use when you sell to newly formed Texas companies or watch new entrants in a Texas city, ZIP or county. Do not use for other states, for officer/owner names or for sole proprietors that do not owe franchise tax. Parameters: daysBack or charterFrom/charterTo (future effective dates are kept, so a recent window can include dates ahead of today); cities, zipPrefixes and countyCodes (Comptroller numbers, e.g. 101 Harris, 227 Travis) narrow the area; orgTypes (e.g. CL LLC, CT corporation) and nameContains filter the entity; activeOnly (default true) keeps right-to-transact active rows; requireSosNumber drops rows with no SOS file number; maxResults caps billed businesses (hard max 5000). Runs with no matches are free. Returns per item: agentSummary, taxpayerNumber, name, address, city, state, zip, countyCode, orgTypeCode, orgType, sosFileNumber, charterDate, responsibilityDate, sosStatus, rightToTransact, naics, sourceUrl, taxpayerUrl; plus TXBIZ_XLSX/CSV.

Behavior: read-only; runs the Apify Actor pandadad0214/texas-new-business-leads (https://apify.com/pandadad0214/texas-new-business-leads) on your own Apify account. Price: $0.0015 per business 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": "texas_new_business_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
citiesNoCities. Taxpayer city, e.g. Houston, Austin, Dallas, San Antonio, Fort Worth.
daysBackNoChartered / responsible in the last N days. Default 7. Matches SOS charter date OR franchise-tax responsibility beginning date. Future effective dates are kept. Use 1 on a daily schedule.
orgTypesNoOrganization types. Empty = all types.
charterToNoOn or before. Optional YYYY-MM-DD.
activeOnlyNoOnly active (right to transact). Keep rows with right-to-transact code A and SOS status A (or blank SOS status).
maxResultsNoMaximum results. You pay per business returned, so this also caps the cost. Default 500; hard max 5000.
charterFromNoOn or after. Optional YYYY-MM-DD; overrides days back. Applied to charter or responsibility date.
countyCodesNoCounty codes. Texas Comptroller county codes as numbers, e.g. 101 (Harris), 227 (Travis), 57 (Dallas), 15 (Bexar), 220 (Tarrant).
zipPrefixesNoZIP prefixes. e.g. 770 (Houston), 787 (Austin), 752 (Dallas), 782 (San Antonio).
nameContainsNoName contains. Case-insensitive substring, e.g. roofing, realty, trucking.
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.
requireSosNumberNoOnly with an SOS / COA file number. Skip taxpayers that have no Secretary of State or Certificate of Authority file number.
run_timeout_secsNoOptional. Seconds to wait for results (default from PANDA_TIMEOUT_SECS, 120; max 300).
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. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that this runs the Apify Actor on the caller's own account, is read-only, charges $0.0015 per business returned, does not charge per result for empty runs, enforces a spending cap, and can take 5-15 seconds or longer. It also explains run_max_items/maxResults billing interaction and timeout behavior, which the annotations do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is long but tightly organized: purpose, sibling contrast, usage/exclusions, parameter semantics, billing/run behavior, and return shape. The density is justified by 14 parameters and a paid external actor, and there is little wasted wording.

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 returned item fields and the wrapper JSON shape {actor, count, items}, plus billing and timeout caveats. For a complex billed data-retrieval tool, an agent has enough information to call it correctly and understand cost/result behavior.

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%, so the baseline would be 3, but the description adds meaning beyond the schema: future effective dates are kept, county codes are Comptroller numbers, run_max_items fills maxResults when unset, and raising maxResults can bill more than is returned. That extra billing and date-window nuance is genuinely useful, though some parameter detail is duplicated from 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?

The description states a specific verb and resource: list new Texas businesses from Texas Comptroller active franchise taxpayer open data, matched on SOS charter date or franchise-tax responsibility date. It explicitly contrasts itself with florida_new_business_leads and local_business_leads, so an agent can distinguish it from siblings before 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?

It gives explicit when-to-use guidance for sellers targeting newly formed Texas companies and watchers of new entrants by city, ZIP, or county. It also gives explicit exclusions: other states, officer/owner names, and sole proprietors that do not owe franchise tax.

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