Skip to main content
Glama

Metadata MCP Connector

Create Facebook Native Criteria Audience

create_facebook_native_criteria_audience

Create a Facebook native criteria audience using Facebook-supported targeting criteria. Build audiences based on Facebook native industries, geographic location, job titles, interests, and age range.

            ESTIMATE-ONLY MODE:
            Pass estimate_only=true to preview audience size WITHOUT creating the audience. In this mode the tool
            returns expectedNumberOfContacts. Default is false.

            ALSO KNOWN AS: Facebook audience, FB criteria audience, native Facebook targeting, Facebook lead audience

            KEYWORDS: Facebook, native, criteria, audience, industry, location, job title, interest, age, lead, targeting

            WHEN TO USE:
            - Create targeted Facebook audiences using native Facebook criteria
            - Target users by Facebook industry categories (e.g., IT and Technical Services, Sales, Management)
            - Target by geographic countries, job titles, interests, and age range
            - Build lead generation audiences for Facebook campaigns

            INDUSTRIES:
            Facebook native industry categories - provide the industry name as a string:
            Administrative Services, Architecture and Engineering, Arts Entertainment Sports and Media,
            Business and Finance, Business decision maker titles and interests, Cleaning and Maintenance Services,
            Community and Social Services, Computation and Mathematics, Construction and Extraction,
            Education and Libraries, Farming Fishing and Forestry, Food and Restaurants,
            Government Employees (Global), Healthcare and Medical Services, Installation and Repair Services,
            IT and Technical Services, Large business-to-business enterprise employees (500+ employees),
            Legal Services, Life Physical and Social Sciences, Management,
            Medium business-to-business enterprise employees (200 - 500 employees), Production, Sales,
            Small business-to-business enterprise employees (10-200 employees), Transportation and Moving

            PARAMETERS:
            - name: Audience name (required)
            - min_age: Minimum age for targeting (required) - must be between 21 and 65
            - max_age: Maximum age for targeting (required) - must be between 21 and 65, and >= min_age
            - industries: Array of Facebook native industry names (optional)
            - countries: List of country names for location targeting (optional) - each must match a country from the platform's supported countries list
            - job_titles: Array of free-text job title strings (optional) - e.g., ["Software Engineer", "Product Owner"]
            - interests: Array of free-text interest strings (optional) - e.g., ["Java", "Python", "Cloud Computing"]

            RETURNS:
            Parsed audience criteria with resolved Facebook reference IDs and validated parameters.

            IMPORTANT NOTES:
            - name, min_age and max_age are required, all other parameters are optional
            - Industries must be valid Facebook native industry names from the enum list
            - Countries must be valid country names from the platform's supported countries list
            - min_age and max_age must both be between 21 and 65, with min_age <= max_age
            - Job titles and interests are free-text arrays
            - Job titles and interests are validated by the backend API with the regex pattern [A-Za-z0-9 ]+ (only ASCII letters, digits, and spaces are allowed). Non-ASCII characters, hyphens, and special characters will be automatically replaced with spaces before resolving references (e.g., "co-founder" becomes "co founder"). When providing job titles or interests, use only alphanumeric characters and spaces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAudience name (required).
max_ageYesMaximum age for audience targeting. Must be between 21 and 65, and greater than or equal to min_age.
min_ageYesMinimum age for audience targeting. Must be between 21 and 65, and less than or equal to max_age.
countriesNoList of country names to target. Each must be a valid country name (e.g., ['United States', 'Brazil']). Resolved to platform country IDs before submission.
interestsNoFree-text interest strings for targeting. Example: ['Java', 'Python', 'Cloud Computing', 'Machine Learning']
industriesNoFacebook native industry categories for audience targeting. Valid values: Administrative Services, Architecture and Engineering, Arts, Entertainment, Sports and Media, Business and Finance, Business decision maker titles and interests, Cleaning and Maintenance Services, Community and Social Services, Computation and Mathematics, Construction and Extraction, Education and Libraries, Farming, Fishing and Forestry, Food and Restaurants, Government Employees (Global), Healthcare and Medical Services, Installation and Repair Services, IT and Technical Services, Large business-to-business enterprise employees (500+ employees), Legal Services, Life, Physical and Social Sciences, Management, Medium business-to-business enterprise employees (200 - 500 employees), Production, Sales, Small business-to-business enterprise employees (10-200 employees), Transportation and Moving. Example: ['IT and Technical Services', 'Sales']
job_titlesNoFree-text job title strings for targeting. Example: ['Software Engineer', 'Senior Developer', 'Product Owner']
estimate_onlyNoIf true, do NOT create the audience — only estimate its size and return the expected contact count. Use this when the user wants to preview Facebook audience size before committing. Defaults to false (audience is created).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate it's a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds valuable behavioral context: estimate_only mode that avoids creation, regex-based validation with automatic replacement of special characters in job titles/interests, and return of resolved Facebook reference IDs. This goes beyond annotations without contradicting them.

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 long but well-organized into labeled sections (ESTIMATE-ONLY MODE, WHEN TO USE, PARAMETERS, IMPORTANT NOTES). It front-loads the core purpose and then provides necessary details. While verbose, each section serves a purpose and avoids redundancy with the schema, though the full industry list is repeated in both schema and description.

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 complex tool with 8 parameters, 3 required, and no output schema, the description covers all necessary context: required vs optional fields, constraints, validation rules, the estimate-only behavior, and what the return value contains. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds substantial meaning: it clarifies age bounds (21–65), lists valid industry names, explains the regex pattern and character replacement for free-text fields, and notes that countries must match the supported list. This is genuine added value beyond the schema's basic descriptions.

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 clearly states the action (create), the resource (Facebook native criteria audience), and the targeting dimensions (industries, location, job titles, interests, age). It distinguishes from sibling tools like create_linkedin_native_criteria_audience by explicitly focusing on Facebook. The 'ALSO KNOWN AS' and 'KEYWORDS' reinforce its identity.

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?

Provides a 'WHEN TO USE' section listing specific use cases (target by Facebook industry, country, job title, etc.) and explains the estimate_only mode for previewing without creation. However, it doesn't explicitly contrast with alternative audience creation tools (e.g., create_bombora_audience) or state when NOT to use it, so it falls just short of full differentiation.

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.

Resources