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

            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.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond the schema: it returns complete configuration, requires all IDs to exist, IDs must be positive integers, and multiple audiences can be requested in one call. It does not fully disclose potential size limits or error behavior, but the added detail is substantial.

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-structured with clear headings: WHEN TO USE, PARAMETERS, AUDIENCE ID SOURCES, EXAMPLE WORKFLOW, RETURNS, and IMPORTANT NOTES. It is front-loaded with the core purpose, though the RETURNS section somewhat repeats the earlier bullet list of what the tool returns, adding mild redundancy.

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 single-parameter, read-only tool with no output schema, the description is complete. It covers the full workflow from discovering audience IDs to calling the tool, lists return content in detail, documents the valid ID constraint, and notes multi-ID support. An agent has everything needed to select and invoke the tool correctly.

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 description coverage is 100% and the sole parameter audience_ids already has a clear array description and example. The tool description reinforces this with the same example, explicitly notes that IDs must be positive integers and valid, and clarifies that multiple IDs can be requested at once, adding practical meaning beyond 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: 'Get detailed information about audiences including criteria and advanced configuration.' It explicitly differentiates from the basic summary and from sibling get_audience_details by framing this tool as the deep-level counterpart. The bullet list of returned configuration details makes the purpose unmistakable.

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?

The WHEN TO USE section lists concrete scenarios, and the AUDIENCE ID SOURCES and EXAMPLE WORKFLOW sections tell the agent to call get_audience_details first to obtain IDs. This is explicit guidance on the prerequisite workflow and how this tool relates to an alternative sibling, leaving little to inference.

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?