Skip to main content
Glama
Sign In
GrowSurf MCP Server

GrowSurf MCP Server

Official
by growsurf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Program Custom Domain

growsurf_set_campaign_custom_domain
DestructiveIdempotent

Configure the hostname used for a GrowSurf program's landing pages and replace an existing domain when needed; the old domain stops loading immediately after replacement.

Instructions

Set or replace the custom domain for your GrowSurf program's landing pages. Pass a hostname such as refer.example.com in domain; https:// is added if you leave it out. Paths, ports, queries, and http:// return 400. Replacing a domain removes the old one right away, and its pages stop loading there, so confirm with the customer before replacing a domain that is already set. Sending the current domain again changes nothing. A domain used by another program returns 409, and 403 means the account cannot use custom domains yet: a higher plan is needed, or for an affiliate program, a payment method on file. A new domain starts unverified: add the CNAME record from the returned dnsRecord at the DNS provider (dnsRecord.name pointing to dnsRecord.value), then call growsurf_verify_campaign_custom_domain. 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": {
      "domain": "<domain>",
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_set_campaign_custom_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe hostname to serve the program's landing pages from, with or without `https://`, such as `refer.example.com`.
campaignIdYesTarget program (campaign) id for this call. 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. Addedv0.19.27

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint and idempotentHint, and the description corroborates both with concrete detail: the old domain's pages stop loading immediately on replace, and re-sending the current domain is a no-op. It goes further by mapping 400/409/403 to specific causes (malformed hostname, domain owned by another program, plan or payment-method restriction) and describing the unverified-DNS state after creation.

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 the action, then hostname format, then side effects, then error semantics, then the DNS follow-up. Dense but nearly every sentence carries decision-relevant information; the error-code enumeration is the only mildly list-like portion, and it earns its place.

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 destructive two-parameter mutation with an output schema, the description covers the mutation's blast radius, input format, failure modes, and the required post-call DNS/verify workflow, and it points at the returned dnsRecord rather than re-documenting the output shape.

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 baseline is 3, but the description adds real constraints the schema omits: `https://` is auto-prepended, while paths, ports, queries, and `http://` are rejected. It also restates the campaignId fallback to GROWSURF_CAMPAIGN_ID in operational terms.

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 precise verb and resource ('Set or replace the custom domain for your GrowSurf program's landing pages') and scopes it to landing-page hostnames. It is clearly separable from the sibling domain tools, and it explicitly names growsurf_verify_campaign_custom_domain as the follow-up step.

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

Usage Guidelines5/5

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

Gives explicit when-to-use conditions plus an exclusion: 'confirm with the customer before replacing a domain that is already set' and 'sending the current domain again changes nothing'. It also routes the agent to the verification tool after a successful set, which is the natural alternative path.

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