Skip to main content
Glama

B2C Listgen Estimate Mcp Tool

b2c_listgen_estimate
Read-onlyIdempotent
Estimate consumer audience sizes using Versium's Consumer Audience Builder (B2C Listgen) API. Supports the full configuration and demographic filter set

For fields with large, high-cardinality option sets (e.g. esthhldincome), use the Consumer Audience Options tool to retrieve available values
Any property restricted to `enum: ["Y"]` is enabled by sending `"Y"`. For example, pet owners who golf in Washington use `{"state":["WA"],"d_pets":"Y","d_golf":"Y"}`.
Call `b2c_listgen_options` with `field: "attribute_flags"` when you need the human-readable meanings of those flag names.

**Tips for Best Results:**
- Start with a single output type and add filters incrementally
- Combine geography with age, income, or lifestyle filters for precise targeting
- Leverage lifestyle and interest filters to reach specific consumer segments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
d_ageNoAge range in years (single value or min-max, e.g., "35-45")
d_lorNoLength of residence in years (single value or range)
d_zipNoArray of 5-digit ZIP codes to filter by
d_golfNo
d_newsNo
d_petsNo
d_sohoNo
d_stateNoArray of 2-letter state codes to filter by
d_countyNoArray of county,state combinations (e.g., "King, WA")
d_genderNoGender filter (M=Male, F=Female)
d_travelNo
d_fishingNo
d_huntingNo
d_ownrentNoHome ownership status codes (H=Owner, R=Renter, 9=Probable Owner)
d_exerciseNo
d_languageNoLanguage codes. See values in options tool
d_networthNoEstimated net worth range using codes. See values in options tool
d_religionNoReligion codes. See values in options tool
d_shootingNo
d_auto_yearNoAutomobile year range (single year or min-max)
d_educationNoEducation level codes: A=High School, B=College, C=Graduate, D=Technical/Vocational
d_gardeningNo
d_hhld_sizeNoHousehold size range (1-9, e.g., "2-4"); 9 means 9 or more
d_home_yearNoYear home was built (single year or range)
d_magazinesNo
d_refi_dateNoRefinance date or date range using YYYYMMDD format
max_recordsNoCap the number of records returned by the eventual list build
d_city_stateNoArray of city,state combinations (e.g., "Seattle, WA")
d_home_valueNoHome value range. See values in options tool
d_occupationNoOccupation codes. See values in options tool
d_weightlossNo
max_coverageNoRequest append processing for selected channels (must overlap required/optional fields)
cfg_zipradiusNoRadius expansion (pseudo-miles) applied around supplied ZIP or city/state centers
d_creditlinesNoNumber of credit lines range (e.g. "0-5")
d_electronicsNo
d_ethnicgroupNoEthnic group codes. See values in options tool
d_hhldveteranNo
d_loantovalueNoLoan-to-value percentage as single value or range (0-100)
d_motorcyclesNo
d_refi_amountNoRefinance amount in thousands (single value or range)
d_senior_hhldNo
d_apparel_mensNo
d_creditratingNoCredit rating range. See values in options tool
d_donation_envNo
d_dwellingtypeNoDwelling type codes (M=Multi Family, S=Single Family, U=Unknown)
d_num_childrenNoNumber of children range (0-8, e.g., "2-3")
d_singleparentNo
d_workingwomanNo
d_esthhldincomeNoEstimated household income range using codes. See values in options tool
d_maritalstatusNoMarital status codes (M=Married, S=Single, A=Married (Inferred), B=Single (Inferred))
d_mortgage_rateNoMortgage interest rate percentage (e.g., "6.75%", "10%")
optional_fieldsNoOptional contact fields to include when available
required_fieldsNoRequired output contact fields. Must include at least one. Recommended to include address for estimate calls for geo info. IMPORTANT: Unlike the B2B Persona API, this field along with optional_fields are used to define output instead of the "output" parameter
cfg_require_nameNoSet to true to require full names in the output
d_apparel_womensNo
d_auto_makemodelNoAuto make and model combo(s) (e.g. "Ford:Escape")
d_mailorderbuyerNo
d_mortgage2_dateNoSecond mortgage date in YYYYMMDD format
d_mortgage2_rateNoSecond mortgage interest rate percentage
d_refi_loan_typeNoRefinance loan type codes. See values in options tool
d_refi_rate_typeNoRefinance rate type codes. A=Adjustable, B=Balloon, F=Fixed, U=Unknown
cfg_require_emailNoSet to true to require email addresses in the output
cfg_require_phoneNoSet to true to require phone numbers in the output
contacts_per_addrNoMaximum contacts per street address (0=unlimited, 1=one contact per address)
d_cardholder_bankNo
d_donation_healthNo
d_lifestyle_musicNo
d_mortgage_amountNoMortgage amount in thousands (use values like "50" or "400")
d_onlinepurchaserNo
d_political_partyNoPolitical party affiliation values
d_youngadult_hhldNo
rcfg_phone_formatNoSet to 1 to prefix returned phone numbers with the country code
d_donation_animalsNo
d_home_improvementNo
d_investing_activeNo
d_lifestyle_sportsNo
d_military_historyNo
d_mortgage2_amountNoSecond mortgage amount in thousands
cfg_require_addressNoSet to true to require mailing addresses in the output
cfg_zipradius_focusNoLimits radius expansion to ZIP, city/state, or none
d_donation_childrenNo
d_donation_intl_aidNo
d_donation_religionNo
d_donation_veteransNo
d_home_market_valueNoHome market value range. See values in options tool
d_lifestyle_cookingNo
d_lifestyle_outdoorNo
d_lifestyle_readingNo
d_cardholder_upscaleNo
d_donation_communityNo
d_donation_politicalNo
d_home_purchase_dateNoHome purchase date in YYYYMMDD format
d_lifestyle_antiquesNo
d_mortgage_rate_typeNoMortgage rate type codes. A=Adjustable, B=Balloon, F=Fixed, U=Unknown
include_filter_attrsNoInclude selected filter attributes as columns in the final audience
d_home_purchase_priceNoHome purchase price in thousands
d_mortgage2_loan_typeNoSecond mortgage loan type codes. See values in options tool
d_mortgage2_rate_typeNoSecond mortgage rate type codes. A=Adjustable, B=Balloon, F=Fixed, U=Unknown
d_donation_unspecifiedNo
d_lifestyle_decoratingNo
d_presence_of_childrenNo
d_donation_arts_cultureNo
d_donation_env_wildlifeNo
include_demo_categoriesNoDemographic category summaries to include in the response. Recommended to include at least one with estimate calls for audience insights in the preview response
d_lifestyle_arts_generalNo
d_mortgage_purchase_dateNoMortgage purchase date in YYYYMMDD format
d_lifestyle_health_beautyNo
d_donation_political_liberalNo
d_donation_political_conservativeNo
d_mortgage_purchase_loan_type_codeNoMortgage purchase loan type codes. See values in options tool

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsNo
query_idNo
warningsNo
input_queryNo
num_matchesNo
num_resultsNo
match_countsNo

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral detail beyond annotations, such as the uniform 'Y' flag convention and a concrete example showing how to combine filters. It does not contradict the annotations.

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?

The description is longer than average but earns its length given the tool's 110 parameters. It front-loads the core purpose, then adds compactly organized behavioral guidance and tips in a scannable bullet list. Minor redundancy exists in 'Supports the full configuration and demographic filter set,' but overall it is well structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a high-complexity tool with 110 parameters, rich annotations, and an output schema. The description provides the essential operational context: where to look up option values, how to interpret Y flags, and how to approach filter construction. It does not explain everything, but the combination of schema, annotations, and description is adequate for correct invocation.

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?

With only 53% schema description coverage, the description helps fill gaps: it explains the semantics of the many undocumented 'Y' enum parameters, points to the options tool for high-cardinality fields, and provides a working filter example. While not every parameter is individually described, the cross-cutting guidance substantially compensates for the schema's omissions.

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 opens with a specific verb-resource pair: 'Estimate consumer audience sizes using Versium's Consumer Audience Builder (B2C Listgen) API.' This clearly distinguishes it from sibling tools like b2c_listgen_options and the B2B-focused b2b_listgen_estimate, and the consumer/B2C framing reinforces when it applies.

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?

The description gives explicit routing guidance for related tools: use the Consumer Audience Options tool for high-cardinality values and call b2c_listgen_options for attribute flag meanings. It does not explicitly contrast with every sibling, like b2b_listgen_estimate or list-building tools, but the purpose and alternatives are largely clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: list generation (B2B vs B2C), enrichment (contact, demographic, firmographic, C2B, IP-to-domain), project/list management, job lifecycle, and validation. No two tools appear to do the same thing, so an agent can reliably select the correct one.

Naming Consistency5/5

All tool names follow the verb_noun pattern consistently, using verbs like list, show, create, preview, search, validate, append, and estimate. Even the segmented append tools (c2b_append, contact_append, demographic_append, firmographic_append, ip_to_domain_append) follow the same pattern with clear noun modifiers. No mixed conventions or vague verbs.

Tool Count4/5

With 19 tools, this is on the higher side but still well-scoped for a data enrichment and list-building platform. The count covers distinct functional areas (audience estimation, enrichment, job/project management, list inspection, documentation) without unnecessary bloat. It feels slightly heavy but each tool earns its place.

Completeness4/5

The tool surface covers the core workflows: estimating audiences, creating and monitoring jobs, managing projects and lists, and enriching records with various data types. Minor gaps exist, such as no explicit delete/update operations for projects or lists, and no direct file download for list contents (though preview_list and show_list provide partial coverage). These are non-blocking gaps that agents can work around.

Resources