GrowSurf

Get Program Custom Domain

growsurf_get_campaign_custom_domain

Read-onlyIdempotent

Fetch the custom domain that serves your GrowSurf program's landing pages, such as https://refer.example.com. Returns domain (null when none is set), isVerified, verifiedAt, and dnsRecord, the CNAME record to add at the DNS provider. This read does not check DNS; use growsurf_verify_campaign_custom_domain for a live 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_get_campaign_custom_domain"
  }
}

Input Schema

Name	Required	Description	Default
`campaignId`	Yes	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.

Output Schema

Name	Required	Description
`domain`	No	The custom domain, such as `https://refer.example.com`, or `null` when none is set.
`createdAt`	No	When the domain was set, in epoch milliseconds. `null` when no domain is set.
`dnsRecord`	No	The DNS record to add at the DNS provider. `null` when no domain is set.
`updatedAt`	No	When the domain record last changed, in epoch milliseconds. `null` when no domain is set.
`isVerified`	No	Whether the domain's `CNAME` record pointed to `dnsRecord.value` at the last check. Landing pages load on the domain only when this is `true`.
`verifiedAt`	No	When the DNS check passed, in epoch milliseconds. `null` while unverified.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description goes further by disclosing that DNS is not validated, that `domain` may be `null`, and that `dnsRecord` is a CNAME to be added at the DNS provider. The stale-vs-live distinction is exactly the behavioral nuance an agent needs before deciding to trust or re-verify the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what is fetched and what shape it returns, followed by the DNS caveat and the targeting rule. No filler and no repetition of annotation-only facts.

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 single-parameter read with an output schema, every decision an agent must make is covered: what comes back, that a null means unconfigured, what to do with `dnsRecord`, and where to go for verification. Nothing material is left unstated.

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 the description's targeting sentence largely restates the schema's own note about `GROWSURF_CAMPAIGN_ID`. It adds no format, validity, or edge-case detail beyond what the parameter definition already provides, so this is the baseline rather than an above-baseline score.

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?

Uses a specific verb ("Fetch") on a specific resource ("the custom domain that serves your GrowSurf program's landing pages") and immediately anchors it with a concrete example URL. It is clearly distinct from the sibling tools that set, remove, or verify the same domain.

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?

Explicitly states the boundary condition: "This read does not check DNS; use `growsurf_verify_campaign_custom_domain` for a live check," naming the alternative and the situation that selects it. It also states the targeting rule (`campaignId` if supplied, otherwise `GROWSURF_CAMPAIGN_ID`), so no inference is needed.

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

All GrowSurf tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.