Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Update Program Emails

growsurf_update_campaign_emails
DestructiveIdempotent

Update GrowSurf campaign Email tab content in place, including sender name, reply-to, subjects, and bodies; omitted fields stay unchanged. Read the Emails tab first for exact field names.

Instructions

Update writable Emails tab fields for your GrowSurf program under fields, in their existing nested shape. settings.sender.fromEmail is read-only; sender address changes require domain verification in the dashboard. settings.sender.fromName and settings.sender.replyToEmail accept non-empty strings, not null. Omit either field to keep its current value, including an unset value returned by a read. The invite and transactional email isEnabled toggles are read-only. An email subject cannot be empty. Email bodies require their template links and footer tokens. When settings.design.layoutMode is INLINE, each body must include {{emailFooter}}; {{emailHeader}} is optional. layoutMode is read-only. Omitted fields retain their existing content; arrays replace wholesale. One call can change many fields, so send related changes together instead of one field per call. Read growsurf_get_campaign_emails first and use its field names and allowed values exactly. An invalid field returns an error that names the field. Targets campaignId if supplied, otherwise GROWSURF_CAMPAIGN_ID.

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

Input Schema

NameRequiredDescriptionDefault
fieldsYes
campaignIdYesTarget program id for this call: the `id` returned by `growsurf_list_campaigns`, not the program name or a share URL. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.33
    • changedInput schema / properties / campaignId / description
      Previous value: -"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."New value: +"Target program id for this call: the `id` returned by `growsurf_list_campaigns`, not the program name or a share URL. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."
  2. Changed4 schema fields changedv0.19.15
    • addedInput schema / properties / campaignId / minLength
      Added value: +1
    • addedInput schema / properties / fields / properties / settings / properties / sender / properties / fromName / description
      Added value: +"Sender name, up to 100 characters. Must not be blank or an email address. Omit to keep the current value; `null` cannot clear it."
    • addedInput schema / properties / fields / properties / settings / properties / sender / properties / replyToEmail / description
      Added value: +"Valid reply-to email address, up to 100 characters. Omit to keep the current value; `null` cannot clear it."
    • changedInput schema / required
      Previous value: -[
      -  "fields"
      -]New value: +[
      +  "fields",
      +  "campaignId"
      +]
  3. Changed1 schema field changedv0.19.9
    • changedInput schema / properties / campaignId / description
      Previous value: -"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Pass the `id` returned by growsurf_create_campaign to configure or operate a program you just created, without restarting the server."New value: +"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."
  4. Changed1 schema field changedv0.19.8
    • addedInput schema / properties / fields / properties
      Added value: +{
      +  "settings": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "sender": {
      +        "additionalProperties": true,
      +        "description": "Patch `fromName` or `replyToEmail`. Change the read-only `fromEmail` in the dashboard after domain verification.",
      +        "not": {
      +          "required": [
      +            "fromEmail"
      +          ]
      +        },
      +        "properties": {
      +          "fromName": {
      +            "type": "string"
      +          },
      +          "replyToEmail": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      }
      +    },
      +    "type": "object"
      +  }
      +}
  5. First observedv0.12.2

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by naming the read-only members (`settings.sender.fromEmail`, `layoutMode`, invite/transactional `isEnabled`), the dashboard domain-verification requirement, the constraint that `fromName`/`replyToEmail` reject `null`, the layout-conditional `{{emailFooter}}` body requirement, and the error behavior for invalid fields. It also discloses mutation semantics the hint bits cannot convey: omitted fields persist while arrays replace wholesale.

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?

Dense but front-loaded: the verb and target come first, followed by hard constraints in descending priority. A few clauses restate what the schema already declares (non-empty `fromName`/`replyToEmail`, omission preserving values), which is slight redundancy but not wasted space in a rules-heavy mutation.

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?

Covers everything an agent needs to call this destructive, idempotent mutation correctly: target resolution, the read-first workflow, per-field writability, conditional body requirements, and error behavior, while an output schema handles return values.

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

Parameters5/5

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

With only 50% schema coverage, the description compensates by explaining the nested `fields` shape, which members are writable versus read-only, that arrays replace wholesale, and how `campaignId` falls back to `GROWSURF_CAMPAIGN_ID` when omitted. This adds real meaning beyond the two documented schema parameters.

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 ("Update writable Emails tab fields for your GrowSurf program under `fields`") and immediately scopes it to the writable subset in their existing nested shape. An agent can distinguish it from the read path (`growsurf_get_campaign_emails`) and from design/options/reward update siblings without opening the 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?

Gives a concrete prerequisite ("Read `growsurf_get_campaign_emails` first and use its field names and allowed values exactly") plus batching guidance ("send related changes together instead of one field per call"). It does not state when a different update tool is required, but for a tab-specific mutation the guidance is strong and actionable.

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