Metadata MCP Connector

Unarchive Audience

unarchive_audience

Unarchive (restore) a previously archived custom audience on the Metadata platform. Use this tool when the user wants to unarchive, restore, or reactivate a custom audience.

                    You can identify the audience either by its numeric custom_audience_id or by its name.
                    If only the audience name is provided, the tool will search existing audiences to resolve the correct ID before unarchiving.

                    PARAMETERS:
                    • custom_audience_id (optional): The numeric ID of the custom audience to unarchive.
                    • audience_name (optional): The name of the custom audience to unarchive. Used to look up the ID if custom_audience_id is not provided.

                    At least one of custom_audience_id or audience_name must be provided.

                    RESPONSE:
                    • actionStatus: "SUCCEEDED" if the audience was unarchived successfully.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`audience_name`	No	The name of the custom audience to unarchive. If provided without custom_audience_id, the tool will search for the audience by name to resolve the ID.
`custom_audience_id`	No	The numeric ID of the custom audience to unarchive.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only/destructive hints, and the description adds notable behavior: name-based ID resolution ('search existing audiences to resolve the correct ID') and the response format (actionStatus: SUCCEEDED). It does not cover failure or not-found behavior, but provides meaningful operational transparency beyond 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 front-loaded with a clear purpose and uses labeled PARAMETERS/RESPONSE sections for easy scanning. It is somewhat verbose and repeats schema fields, but every major section contributes useful operational or constraint information.

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?

For a two-optional-parameter tool with no output schema, the description covers input selection, ID resolution behavior, the at-least-one requirement, and the success response. It does not describe error cases or prerequisites (e.g., audience must currently be archived), but the provided context is largely sufficient.

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 coverage is 100%, but the description adds the critical constraint that 'At least one of custom_audience_id or audience_name must be provided' and explains their fallback relationship. This goes beyond the schema, which marks both as optional with no required-count validation.

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?

Description opens with 'Unarchive (restore) a previously archived custom audience on the Metadata platform,' stating a precise verb, resource, and action. This clearly differentiates from the sibling archive_audience by emphasizing restoration/re-activation of a previously archived audience.

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?

Explicitly states 'Use this tool when the user wants to unarchive, restore, or reactivate a custom audience,' giving clear when-to-use context. It does not explicitly name exclusions or alternative tools like archive_audience, so it misses the full when-not boundary.

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?