Metadata MCP Connector

Get Deep Audience Details

get_deep_audience_details

Read-only

Get detailed information about audiences including criteria and advanced configuration.

            This tool returns comprehensive audience data beyond the basic summary, including:
            - Complete audience criteria and targeting configuration
            - Segment information and settings
            - Lookback window configuration
            - Advanced configuration details and metadata
            - Full audience structure and composition

            **WHEN TO USE:**
            - Retrieve complete audience criteria and configuration
            - Analyze detailed targeting setup for an audience
            - Export or review full audience specifications
            - Understand advanced audience configuration
            - Compare detailed configuration across multiple audiences

            PARAMETERS:
            - audience_ids: Array of audience IDs to retrieve details for (required)
              Example: [42828, 42829, 42831]

            AUDIENCE ID SOURCES:
            Use the get_audience_details tool first to:
            - List all available audiences in your account
            - Find the IDs of audiences you want detailed information for
            - Get the basic summary before requesting deep details

            EXAMPLE WORKFLOW:
            1. Call get_audience_details() to see all audiences and their IDs
            2. Identify which audiences you need deep details for
            3. Call get_deep_audience_details(audience_ids=[42828, 42831]) to get full configuration

            RETURNS:
            Detailed audience information including:
            - Audience ID, name, and type
            - Complete targeting criteria
            - Segment configuration (if applicable)
            - Lookback window settings
            - Advanced metadata and configuration
            - Full audience composition details
            - companies_summary on a CSV company list (a LinkedIn native CSV or an account list): status (final, matching or failed), list_companies (the platform's stored count, null until final), submitted_companies (rows an account list handed to matching, null on a native list), dropped_by_matching (submitted minus stored, once final), linkedin_organizations (company name criteria on a native list, counted apart from the list) and total. Quote company counts from it, and never report a count that is still matching as final.

            IMPORTANT NOTES:
            - All provided audience IDs must exist and be valid
            - IDs must be positive integers
            - You can request details for multiple audiences in a single call
            - Results include complete audience configuration data

Input Schema

TableJSON Schema

Name	Required	Description	Default
`audience_ids`	Yes	Array of audience IDs to retrieve detailed information for. Example: [42828, 42829, 42831]

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that with validation constraints (all IDs must exist, must be positive integers, multiple IDs allowed in one call) and a RETURNS outline; it does not mention failure behavior when an ID is invalid, so it falls short of a 5.

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

Conciseness3/5

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

Front-loaded and organized under headers, but bloated: PARAMETERS duplicates the schema, IMPORTANT NOTES repeats the minimum:1 constraint, the RETURNS bullets largely duplicate the WHEN TO USE bullets, and an unrelated companies_summary paragraph about CSV company lists is pasted in mid-returns.

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?

With no output schema, the description does carry the return-value burden and does so adequately through the RETURNS section, plus prerequisite guidance via get_audience_details. The mismatched companies_summary passage slightly muddies what the tool actually returns.

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 description coverage is 100% and the single parameter is fully documented, so the baseline is 3. The PARAMETERS block and example array merely restate the schema's own example and add no new syntax or format meaning.

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?

States a specific verb and resource ('Get detailed information about audiences') and explicitly frames scope as richer than the basic summary, which cleanly separates it from the sibling get_audience_details. An agent can pick between the two without opening either 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?

Contains an explicit WHEN TO USE list, an AUDIENCE ID SOURCES note directing the agent to call get_audience_details first, and a numbered example workflow. The routing condition to the sibling tool is stated, not inferred.

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 tools Inspect

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

Need Help?