Skip to main content
Glama

Delete a Meta ad

ads_delete_ad
Destructive

Delete one Meta ad from ads_get_tree. Irreversible; its ad set and campaign stay. Confirm the ad by name with the user first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "adId": "<adId>",
      "adAccountId": "<adAccountId>"
    },
    "name": "ads_delete_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
adIdYesAn ad id from ads_get_tree.
platformNometa_ads, tiktok_ads or linkedin_ads. Needed only when the profile has more than one ad network and no accountId is given.
accountIdNoThe Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection.
profileIdNoA profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree.
adAccountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so irreversibility is partly redundant, but the description adds genuine value by spelling out the blast radius ('its ad set and campaign stay') and an explicit confirmation step before execution. It does not mention permission or rate-limit 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?

Three short sentences: scope first, consequence second, safety requirement last. No filler and the most important constraint is front-loaded.

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 destructive two-required-parameter mutation with no output schema, the description covers scope, irreversibility and confirmation. The remaining gap is the required adAccountId, which has no description in either the schema or the prose.

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?

Schema coverage is 80%, so the baseline applies. The only parameter detail in the description ('adId from ads_get_tree') simply restates the schema's own description; nothing is said about platform, accountId, profileId resolution, or the required adAccountId.

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?

States a specific verb and resource ('Delete one Meta ad') and names the retrieval tool it sources the id from ('from ads_get_tree'). The clause 'its ad set and campaign stay' makes clear this deletes a single ad only, distinguishing it from ads_delete_ad_group and ads_delete_campaign without needing their schemas.

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?

Gives the source of the target ('from ads_get_tree') and a mandatory precondition ('Confirm the ad by name with the user first'), which is concrete when-to-use guidance. It stops short of naming alternative deletion tools or stating when a bulk/parent deletion would be preferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources