Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

ad_manager_fb_delete_campaign

DestructiveIdempotent

Delete a Facebook ad campaign by campaign ID to remove it from GoHighLevel. Resolves the need to clean up or stop campaigns directly via automation.

Instructions

Delete campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYes
locationIdNoLocation identifier Defaults to GHL_LOCATION_ID when omitted.
Behavior3/5

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

Annotations already declare destructiveHint: true and readOnlyHint: false, so the agent knows this is a mutation. The description adds no further behavioral detail (e.g., permanence, impact on ads). It does not contradict annotations, and since annotations cover the core behavior, the description's lack of additional context is acceptable but not helpful.

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 extremely minimal, essentially a label rather than a structured sentence. It is not appropriately sized because it omits essential context; this is under-specification rather than conciseness.

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 destructive tool with two parameters and no output schema, the description lacks any mention of consequences, prerequisites, or usage scenarios. It is incomplete and would leave an agent uncertain about side effects and required setup.

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?

The description says nothing about parameters. Schema coverage is 50%: locationId has a description, but campaignId (required) is undocumented. Since coverage is not high, the description should compensate, but it adds no meaning to either parameter.

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 'Delete campaign' uses a specific verb and resource, clearly indicating a delete operation on a campaign. However, it does not differentiate among sibling tools like ad_manager_fb_delete_ad or ad_manager_fb_delete_adset; the distinction is implicit in the tool name rather than the description.

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, no mention of prerequisites, and no caution about the destructive nature. The description provides no context for selecting this tool or avoiding misuse.

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