Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

ad_manager_fb_delete_adset

DestructiveIdempotent

Delete a Facebook ad set by providing its ID. Input the adsetId to remove it from the ad account, with optional locationId for scoping.

Instructions

Delete ad set

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adsetIdYes
locationIdNoLocation identifier Defaults to GHL_LOCATION_ID when omitted.
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description does not need to restate these. However, it adds no context about what happens to the ad set, whether deletion is permanent, or any side effects. The description is consistent with annotations but contributes no extra behavioral transparency.

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?

The description is only three words and under-specified rather than concise. It lacks structure and substance, similar to a tautological restatement of the tool name. It does not provide enough information to be useful.

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?

For a delete operation with required parameters and no output schema, the description is severely incomplete. It omits any details about what is required, consequences, or how to verify deletion. An agent would need to rely entirely on the schema and annotations.

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

Parameters2/5

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

Schema description coverage is 50% (locationId has a description, adsetId does not). The tool description does not mention any parameters, so it fails to compensate for the missing adsetId documentation. It adds no semantic insight beyond the schema.

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

Purpose3/5

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

The description states the verb 'delete' and the resource 'ad set', which is clear and matches the tool name. However, it does not differentiate from sibling delete tools like ad_manager_fb_delete_ad or ad_manager_fb_delete_campaign; it merely restates the name without added specificity.

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 delete_campaign or delete_ad. The description provides no context about prerequisites, conditions, or exclusions.

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/AIWerk/mcp-server-ghl'

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