Skip to main content
Glama

Delete Ad Set

meta_delete_adset
Destructive

Delete an ad set permanently in Meta Ads Manager using its ad set ID.

Instructions

Deletes an ad set permanently.

Args:

  • adset_id (string): Ad set ID to delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adset_idYes
Behavior3/5

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

Annotations already mark destructiveHint=true, indicating a destructive operation. The description adds 'permanently' to emphasize irreversibility, but does not disclose other potential side effects (e.g., associated ads or campaigns). This adds some value 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.

Conciseness5/5

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

The description is extremely concise, consisting of two sentences and a parameter list. Every sentence serves a purpose with no redundancy.

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 deletion tool with one required parameter, the description is fairly complete. It explains the action and the input. However, it could mention any constraints (e.g., cannot delete if ad set is active) or return value for full completeness.

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 provides only the type 'string' for adset_id with 0% description coverage. The description explicitly documents the parameter as 'Ad set ID to delete', adding necessary meaning that the schema alone does not provide.

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 the tool deletes an ad set permanently. It distinguishes from sibling tools like meta_delete_ad and meta_delete_campaign by specifically targeting ad sets.

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?

No guidance is provided on when to use this tool versus alternatives such as pausing or updating an ad set. The description does not mention prerequisites or scenarios where deletion is appropriate.

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/oliverames/meta-mcp-server'

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