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

ghl-mcp-server-v2

by zackscriven

ghl_email_update_campaign

Update an existing email campaign draft's name, editor type, or content to keep campaign details current and accurate.

Instructions

Update Email Campaign Update an email campaign draft Endpoint: PATCH /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>",
      "body": "<body>"
    },
    "name": "ghl_email_update_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
campaignIdYesCampaign ID
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdateEmailCampaignPublicV2BodyDto"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds real context beyond that: the exact endpoint, API version header, the requirement for a Sub-Account (location) token, and the emails/campaigns.write OAuth scope — all of which an agent needs to predict auth failures. It does not explain partial-update/patch semantics or what happens to unspecified fields.

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?

Front-loaded with purpose, then endpoint, then auth in descending priority — a good ordering. Minor redundancy between the title echo 'Update Email Campaign' and 'Update an email campaign draft', but nothing wasted overall.

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

Completeness3/5

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

Auth requirements, endpoint, and draft scoping are covered, and annotations carry the safety profile. Remaining gaps: whether the body supports partial updates, what the response contains (no output schema), and how errors present — for a mutation tool this leaves some inference to the agent.

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%, and every parameter including the nested body fields (name, userId, editorType, editorContent) is documented in the schema, so the description adds nothing parameter-specific. Baseline 3 applies since the schema does the work.

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?

States a specific verb and resource ('Update an email campaign') and narrows the object to a 'campaign draft', which distinguishes it from siblings like ghl_email_create_campaign, ghl_email_delete_campaign, and ghl_email_schedule_campaign. It stops short of explicitly naming those alternatives, so differentiation is implied rather than stated.

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?

The word 'draft' implicitly tells the agent this applies only to unpublished campaigns, which is a useful scope hint. However, there is no explicit when-to-use guidance, no statement about what happens with scheduled or sent campaigns, and no routing to sibling tools such as schedule or delete.

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