Skip to main content
Glama
Sign In
GrowSurf MCP Server

GrowSurf MCP Server

Official
by growsurf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Verify Program Custom Domain

growsurf_verify_campaign_custom_domain
Idempotent

Verify a campaign's custom domain DNS and return whether the CNAME record has propagated in isVerified; retry later if false.

Instructions

Check the program's custom domain DNS now and return the result in isVerified. Call it after the CNAME record from dnsRecord is in place. If the record is wrong or has not propagated yet, isVerified stays false; try again later. The first time the check passes, GrowSurf sets up the domain's SSL certificate, and pages can take a few minutes to load over https:// after that. More than one CNAME record on the hostname returns 400. Returns 404 when no custom domain is set. A domain that is already verified is returned as is, without a new check. 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": {
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_verify_campaign_custom_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.4/5.0
Behavior5/5

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

Discloses substantial behavior beyond the annotations: first successful check triggers SSL certificate provisioning, pages may be slow over https for minutes, duplicate CNAME records yield 400, no custom domain yields 404, and verified domains short-circuit. These side effects are consistent with readOnlyHint=false and idempotentHint=true.

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?

Sentences are front-loaded with the action and result field, then progress to preconditions, failure modes, and side effects. It is dense but nearly every clause carries operational information; only the trailing campaignId sentence duplicates schema content.

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 one-parameter verification tool with an output schema, the description still covers preconditions, error codes, async SSL effects, and the already-verified no-op. An agent has everything needed to call it correctly and interpret failure.

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?

With only one parameter at 100% schema coverage, the schema already documents campaignId and the GROWSURF_CAMPAIGN_ID fallback. The description's final sentence restates that fallback rather than adding new meaning, so it sits at the high-coverage baseline.

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?

Opens with a specific verb and resource: 'Check the program's custom domain DNS now and return the result in `isVerified`.' This clearly separates it from the sibling get/set/remove custom domain tools without needing their schemas.

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 precondition ('Call it after the `CNAME` record from `dnsRecord` is in place') and a retry instruction for propagation delay, plus a no-op case for already-verified domains. It stops short of explicitly naming alternatives like get_campaign_custom_domain for a plain read, but the when-to-call context is unambiguous.

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