Skip to main content
Glama

Update a campaign

update_campaign
DestructiveIdempotent

Use this when the user wants to change a campaign's settings: its name, start, sending days and time zone, lists and exclusions, tracking, daily limits or link. Send at least one. New lists replace the campaign's lists but enroll nobody in a running campaign. Click tracking cannot be turned off while a step waits for a click. It changes settings only, never what the steps say. Free.

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

Input Schema

NameRequiredDescriptionDefault
nameNoA new name.
ctaLinkNoThe link steps insert where they write `{CTA Link}`: an http or https URL, or null or empty for none.
listIdsNoThe campaign's lists, replacing the ones it has, 1 to 10. A running campaign does not enroll a new list's people: adding one list to the campaign does that.
timezoneNoThe IANA time zone the sending days and hours (9:00 to 17:00) are read in, such as `Europe/Lisbon`: a region, not an abbreviation such as EST. UTC when a campaign is created without one.
emailDaysNoThe days messages may go out, by English name with a capital first letter. Monday to Friday when left out.
isDynamicNoEnrolls people added to the campaign's lists after launch, as they arrive. False when left out.
startDateNoWhen sending may start, as an ISO 8601 date-time. Now when left out.
campaignIdYesThe campaign's id.
excludeListsNoUp to 10 people lists whose people are never enrolled, matched by person, email address or LinkedIn profile. An id that is not one of your lists excludes nobody.
dailyEmailLimitNoThe most emails the campaign sends a day, 1 to 10,000, or null for no limit.
excludeContactedNoSkips people your campaigns already wrote to: `none` (the default) skips nobody, `ever` skips everyone written to, and `last_1_month` to `last_1_year` skip those written to in that time.
addUnsubscribeLinkNoEnds every email with a one-click unsubscribe link. True when left out.
excludeCompanyListsNoUp to 20 company or people lists: nobody who works at one of their companies is enrolled. A list the organization does not have answers `422` `exclude_company_lists_invalid`.
clickTrackingEnabledAtNoTurns click tracking on from this ISO 8601 date-time, or off with null. Off when left out. A step that waits for a click needs it on.
excludeEngagedContactsNoSkips people who replied to one of your campaigns. False when left out.
dailyLinkedinMessageLimitNoThe most LinkedIn messages and InMails the campaign sends a day, 1 to 10,000, or null for no limit.
openRateTrackingEnabledAtNoTurns open tracking on from this ISO 8601 date-time, or off with null. Off when left out.
dailyLinkedinConnectionLimitNoThe most LinkedIn invitations the campaign sends a day, 1 to 10,000, or null for no limit.
sendOnlyToValidatedEmailsEnabledAtNoFrom this ISO 8601 date-time, enrolls only people whose email address checked `valid`; null also enrolls catch-all and unchecked addresses.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag the operation as non-read-only, destructive, idempotent and open-world; the description adds the actual risk mechanics: new lists replace existing lists without enrolling anyone in a running campaign, click tracking cannot be disabled while a step awaits a click, and at least one field must be sent. It also discloses that the call is free, which no structured field conveys.

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?

Guidance is front-loaded in the first sentence and every subsequent sentence carries a distinct constraint with no filler. The fragments "Send at least one" and "Free" are compressed to the point of mild ambiguity, which costs a little clarity but no length.

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

Completeness5/5

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

For a 19-parameter mutation with no output schema, the description covers the partial-update contract, the destructive list-replacement effect, the click-tracking constraint, scope exclusion versus step editing, and cost. What remains (field formats, the 422 case) is already carried by the schema, so nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all 19 parameters and the baseline is 3. The description adds cross-parameter meaning the schema lacks, notably the interaction between click tracking and waiting steps and the replacement-not-enrollment behavior of list updates.

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+resource and enumerates the exact setting groups changeable: "its name, start, sending days and time zone, lists and exclusions, tracking, daily limits or link." It then explicitly separates itself from update_campaign_step with "It changes settings only, never what the steps say," so an agent can route correctly without opening either schema.

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

Usage Guidelines4/5

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

"Use this when the user wants to change a campaign's settings" gives clear when-to-use context, and "never what the steps say" functions as an implicit when-not that steers step edits elsewhere. It stops short of naming the alternative tool for step content, so the exclusion must be inferred from the sibling's name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources