Skip to main content
Glama
Sign In

GrowSurf

by com.growsurf
OverviewDiscussionsAdmin

Remove Program Custom Domain

growsurf_remove_campaign_custom_domain
DestructiveIdempotent

Remove the custom domain from your GrowSurf program. Its landing pages stop loading on that domain and go back to their GrowSurf URL. Returns { domain, success }. Returns 404 when no custom domain is set. 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_remove_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
domainNoThe custom domain that was removed.
successNoWhether the custom domain was removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description goes beyond them by spelling out what destruction means in practice: landing pages stop loading on the domain and revert to the GrowSurf URL. It also discloses the return payload and the 404 failure mode, which annotations cannot convey.

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?

Four short sentences, front-loaded with the action and its side effect before the payload and the target-resolution rule. The return-shape sentence is somewhat redundant given the output schema, keeping it just below top marks.

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 destructive mutation, the description covers effect, failure mode, return shape, and target resolution. Nothing an agent needs in order to decide whether and how to call it is missing, even though the output schema already covers returns.

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 schema already explains that campaignId defaults to GROWSURF_CAMPAIGN_ID, so the description's final sentence largely restates structured data. Mild tension remains: the schema marks campaignId as required while the description says 'if supplied, otherwise GROWSURF_CAMPAIGN_ID', which an agent may find ambiguous.

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?

Specific verb ('Remove') plus resource ('the custom domain from your GrowSurf program'), immediately separable from the sibling pair set_campaign_custom_domain and get_campaign_custom_domain. The consequence sentence makes the effect on landing pages unambiguous.

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?

The 404-when-no-domain-is-set note tells the agent the precondition that makes this call meaningful, and the target-resolution sentence tells it how the program is selected. It stops short of explicitly naming set_campaign_custom_domain as the inverse operation, so the alternative routing is left implicit.

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

All GrowSurf toolsInspect
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.

Resources