Skip to main content
Glama
mathieubernardi

meta-mcp-py

delete_custom_audience

Delete a custom audience by ID. Permanently removes the audience from your ad account, with no way to undo.

Instructions

Supprime une audience personnalisée. Action irréversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audience_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does explicitly warn that the action is irreversible, which is a critical behavioral trait. However, it does not mention other aspects such as permission requirements, side effects on related data, or failure behavior.

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

Conciseness5/5

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

The description is extremely concise: two short sentences that state the core action and the most important warning. Every word earns its place and the key information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter delete operation, the description is minimally complete: it names the resource, the action, the required parameter, and warns about irreversibility. However, with no annotations or output behavior details, an agent might still lack clarity on what the response indicates or whether any implicit side effects occur.

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?

The input schema only provides 'audience_id' with type 'string' and no description, so schema description coverage is 0%. The tool description implies that 'audience_id' identifies the custom audience to delete, but it adds no further detail about format, source, or 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?

The description clearly states a specific verb ('Supprime') and resource ('audience personnalisée'), making the tool's purpose unambiguous. It also distinguishes itself from sibling tools like get_custom_audience or remove_users_from_audience by clearly targeting deletion of the entire audience.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions under which deletion is appropriate, or caution against using it when only removing users is needed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mathieubernardi/Meta_Business_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server