Skip to main content
Glama
estapel-ai

mcp-facebook-ads

by estapel-ai

delete_adset

Archive a Facebook ad set by ID to stop it from running and remove it from active campaigns.

Instructions

Archive ad set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adset_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Archive' hints at a soft-delete rather than permanent removal, but it does not disclose whether the action is reversible, what permissions are required, or how associated entities are affected.

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

Conciseness2/5

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

At three words, the description is under-specified rather than concise. It is front-loaded but does not provide enough structure or information for an agent to act on confidently.

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

Completeness2/5

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

Although an output schema exists and need not be described, the definition lacks essential context: when to use it, whether it requires specific permissions, and what 'archive' entails. For a mutation tool with no annotations, this is a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning to the single adset_id parameter. It does not clarify the expected ID format, source, or any constraints, failing to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Archive) and resource (ad set), making the operation identifiable. It does not differentiate from sibling tools like delete_ad, delete_campaign, or update_adset, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives such as update_adset or delete_ad, nor any prerequisites or exclusions. The description simply names the action without context.

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