Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_email_delete_campaign

DestructiveIdempotent

Deletes a specific email campaign in a GoHighLevel sub-account using the location ID and campaign ID.

Instructions

Delete Campaign Delete a campaign Endpoint: DELETE /emails/locations/{locationId}/campaigns/emails/{campaignId} (Version header: v3; source: v3/emails-v3.json) Requires a Sub-Account (location) token. OAuth scopes: emails/campaigns.write

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": {
      "locationId": "<locationId>",
      "campaignId": "<campaignId>"
    },
    "name": "ghl_email_delete_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesCampaign ID
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new operational context: the required Sub-Account token, the specific OAuth scope, the API version header, and the source spec. It stops short of saying whether deletion is permanent or cascades to associated email/statistics data.

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

Conciseness4/5

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

The endpoint and auth requirements are front-loaded and dense with useful detail. Minor waste from the redundant title/verb repetition ('Delete Campaign' followed by 'Delete a campaign') and the source-file citation, which adds little for an agent.

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 two-parameter destructive operation with full annotation coverage and no output schema, the definition covers identity, endpoint, auth, and scope. The only meaningful gap is post-deletion behavior (permanence, cascade, error cases), which would help an agent reason about consequences.

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 description coverage is 100%, with both locationId and campaignId documented and exampled, so the schema does the heavy lifting. The endpoint template does clarify that both are path parameters, but no format or validation guidance is added beyond that — baseline 3 is appropriate.

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 a campaign') and reinforces it with the exact HTTP endpoint DELETE /emails/locations/{locationId}/campaigns/emails/{campaignId}. This is unmistakable against siblings like ghl_email_get_campaign, ghl_email_update_campaign, and ghl_email_list_campaigns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the verb and the endpoint path, and the description supplies prerequisites (Sub-Account/location token, OAuth scope emails/campaigns.write). However it never states when to choose this over alternatives such as ghl_email_update_campaign, nor does it warn about irreversibility.

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

Deploy Server

Other Tools