Metadata MCP Connector

Archive Audience

archive_audience

Destructive

Archive (delete) a custom audience from the Metadata platform. Use this tool when the user wants to archiveo or delete a custom audience from the entire System.

                    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 archiving.

                    PARAMETERS:
                    • custom_audience_id (optional): The numeric ID of the custom audience to archive.
                    • audience_name (optional): The name of the custom audience to archive. 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 archived successfully.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`audience_name`	No	The name of the custom audience to archive. 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 archive.

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 set destructiveHint=true and readOnlyHint=false, and the description consistently reflects this by saying 'Archive (delete).' It adds useful behavioral context beyond the annotations: the tool will resolve audience_name by searching existing audiences before archiving, and it documents the actionStatus response field.

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?

The description is organized into clear PARAMETERS and RESPONSE sections and is mostly front-loaded, but it repeats schema content nearly verbatim and contains a typo ('archiveo'). The extra whitespace and redundant listing of parameters reduce economy without adding much new 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 simple two-parameter destructive tool with full schema coverage, the description covers the essential information: how to identify the audience, the at-least-one-parameter requirement, and the response format. It does not detail failure behavior or irreversibility, but the destructive annotation and 'delete' wording make the core behavior clear.

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?

The schema already fully describes both parameters, so the baseline is 3. The description adds extra value by clarifying the 'at least one of custom_audience_id or audience_name must be provided' constraint and reinforcing the ID-resolution behavior for audience_name.

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 uses a specific verb ('Archive (delete)') and resource ('custom audience from the Metadata platform'), making the tool's purpose unambiguous. It clearly distinguishes itself from related sibling tools like unarchive_audience and archive_ad by targeting custom audiences specifically.

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 explicitly states when to use the tool: 'when the user wants to archive or delete a custom audience.' It also explains the two identification modes (by ID or by name), but does not enumerate alternatives or explicitly state situations where this tool should not be used.

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?