Skip to main content
Glama

Metadata MCP Connector

by io.metadata.mcp-server
OverviewDiscussionsAdmin

Get Matched Audiences

get_matched_audiences
Read-only

Get matched audiences (custom audiences) from the Campaign Wizard based on audience type and targeting options.

                    Retrieves custom audiences that match specific targeting configurations.
                    Use this to find available audiences for campaign targeting on a given advertising channel.
                    This is the canonical tool to call when you need an audience id to attach to a campaign or a target group's include[].audiences / exclude.audiences arrays. Each row is a CHANNEL row: its `id` is the row id, and `customAudienceId` (mirrored as `mdAudienceId`) is the Custom Audience id. For a target group copy `mdAudienceId`, `name`, `type`, `matchCount`, `matchCountType` and `inactive` from the row; NEVER put the row `id` into `mdAudienceId` (the platform cannot resolve it and answers 'Targeting group is too small'). Rows with inactive=true have no live segment on the channel and are refused by the platform; pick an active row or wait for matching to finish. It draws on the same source the main UI's target-group audience-chooser uses, so what this tool returns is what the platform considers attachable.

                    AUDIENCE TARGETING TYPES AVAILABLE:
                    • FIRMOGRAPHIC_INCLUDE: Firmographic inclusion filters (company size, industry, location)
                    • FIRMOGRAPHIC_EXCLUDE: Firmographic exclusion filters
                    • FIRMOGRAPHIC_EXCLUDE_BASIC: Basic firmographic exclusions
                    • FIRMOGRAPHIC_INCLUDE_SFDC: Salesforce firmographic inclusions
                    • NATIVE_TARGETING_CSV: CSV-based native targeting
                    • NATIVE_TARGETING_DYNAMIC: Dynamic native targeting lists
                    • NATIVE_TARGETING_STATIC: Static native targeting lists
                    • CONTACT_LIST: Custom contact list targeting
                    • STORELEADS: Store leads targeting
                    • DYNAMIC_G2: Dynamic G2 crowd data
                    • DYNAMIC_G2_CONTACT: Dynamic G2 contact data
                    • G2_ABM_CONTACT: G2 ABM contact targeting
                    • LEADSIFT: LeadSift intent data targeting
                    • BUYER_INTENT: Buyer intent data targeting
                    • MA_ACCOUNTS_STATIC: Marketing automation static accounts
                    • MA_ACCOUNTS_DYNAMIC: Marketing automation dynamic accounts
                    • MA_CONTACTS_STATIC: Marketing automation static contacts
                    • MA_CONTACTS_DYNAMIC: Marketing automation dynamic contacts
                    • NATIVE_LINKEDIN: Native LinkedIn targeting options
                    • LINKEDIN_RETARGETING: LinkedIn retargeting audiences
                    • SFDC_CONTACTS_DYNAMIC: Salesforce dynamic contacts
                    • SFDC_CONTACTS_STATIC: Salesforce static contacts
                    • SFDC_ACCOUNT_DYNAMIC: Salesforce dynamic accounts
                    • WEBSITE_RETARGETING: Website visitor retargeting
                    • WEBSITE_ACCOUNT_RETARGETING: Website account-based retargeting
                    • TECHNOLOGY: Technology stack targeting
                    • SLINTEL_TECHNOLOGY: Slintel technology targeting

                    COMMON USE CASES:
                    - Find all LinkedIn audiences using firmographic targeting
                    - Get audiences with website retargeting enabled
                    - List audiences using G2 intent data
                    - Search for audiences with Salesforce integration
                    - Identify audiences using specific MA platforms
                    - Find dynamic vs static audience configurations
                    - Discover available contact lists and store leads

                    PARAMETERS:
                    - type: Array of targeting types to match (defaults to all types if not specified)
                    - channel: Advertising channel (LINKEDIN, FACEBOOK, GOOGLE_ADS, INSTAGRAM, TWITTER, YOUTUBE, REDDIT, MICROSOFT_ADS)
                    - page: Page number for pagination (0-indexed)
                    - sort: Sort field and direction (e.g., 'createdDate,desc', 'name,asc')
                    - size: Number of results per page (1-200)

                    RETURNS:
                    Paginated list of custom audiences matching the specified targeting criteria.
                    Each audience includes:
                    - id: Audience ID
                    - name: Audience name
                    - matchCount: Number of matches in the audience
                    - type: Targeting type (e.g., FIRMOGRAPHIC_INCLUDE, MA_CONTACTS_DYNAMIC)
                    - channel: Channel the audience is for
                    - createdDate: When the audience was created
                    - inactive: Whether the audience is active or inactive
                    - tags: Associated tags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (0-indexed)
sizeNoNumber of results per page
sortNoSort field and direction in format 'field,direction'. Common fields: createdDate. Direction: asc or desc.createdDate,desc
typeYesArray of audience targeting types to filter by. If omitted, searches all targeting types.
channelNoThe advertising channel to filter campaigns byLINKEDIN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Even with readOnlyHint=true, the description adds substantial behavioral detail: each row is a CHANNEL row, row id must not be copied into mdAudienceId, inactive=true rows are refused by the platform, and the data comes from the same source as the UI audience chooser. This goes well beyond 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.

Conciseness2/5

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

The description is heavily redundant: the full enum list and parameter details duplicate the input schema, and the 'COMMON USE CASES' section adds little. It is organized with headings and front-loaded with the key purpose, but it is far longer than needed and not every section earns its place.

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?

Without an output schema, the description compensates by listing returned fields and explaining critical row semantics, inactive handling, and the canonical use case. However, the description's claim that type can be omitted conflicts with the required array in the schema, leaving an inconsistency an agent could trip on.

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 coverage is 100%, so the schema already documents all parameters. The description mostly duplicates the schema and adds little accurate new parameter meaning. In fact, it says 'type... defaults to all types if not specified' while the schema marks type as required, which is misleading and could cause incorrect calls.

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 ('Get matched audiences... Retrieves custom audiences that match specific targeting configurations') and explicitly declares this is 'the canonical tool to call when you need an audience id to attach to a campaign or a target group's include[].audiences / exclude.audiences arrays.' This clearly distinguishes it from sibling audience-related tools and states its role.

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 clear context for when to use it: to find available audiences for campaign targeting on a given channel and to obtain an audience id for inclusion/exclusion arrays. It does not explicitly name alternatives or say when not to use it, but the 'canonical tool' phrasing and use-case list provide adequate guidance.

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

All Metadata MCP Connector toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources