GrowSurf

Create Webhook

growsurf_create_campaign_webhook

Add a webhook to your GrowSurf program. payloadUrl is required. events is the list of events this webhook is subscribed to. Omit it to subscribe the webhook to every event its program type offers, or send [] for none. An event the program type does not offer returns 400. A program can have up to 5 webhooks, counting the primary webhook, so you can create up to 4. Creating another returns 400. secret is write-only — GrowSurf uses it to sign deliveries (the GrowSurf-Signature HMAC header) and never returns it. A program can have only one saved Bask Health webhook across all bask.ninja hosts and paths, including disabled webhooks. A second Bask Health webhook returns 400. A concurrent change to webhook settings can return 409; reload the webhooks before retrying. Targets campaignId if you pass it, 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": {
      "payloadUrl": "<payloadUrl>",
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_create_campaign_webhook"
  }
}

Input Schema

Name	Required	Description
`events`	No
`secret`	No	Write-only. Signs deliveries; never returned.
`isEnabled`	No
`campaignId`	Yes	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.
`payloadUrl`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

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."

First observedOct 8, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only supply the generic read-only/idempotent/destructive flags, and the description adds substantial context beyond them: the 5-webhook cap (4 creatable), the one-Bask-Health-webhook constraint, the write-only `secret` used for GrowSurf-Signature HMAC signing, the 409 concurrency behavior, and the 400 conditions. That is exactly the behavioral disclosure a mutation tool needs.

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 required field comes first, then event semantics, limits, `secret`, and targeting. Every sentence carries a distinct constraint, though the Bask Health rule is verbose relative to how often it will matter.

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?

With an output schema present, return values need no explanation, and the description covers prerequisites, caps, error codes, retry behavior, and campaign targeting. For a 5-parameter mutation tool this is essentially complete; only `isEnabled` meaning is absent.

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 40%, and the description compensates well, explaining `payloadUrl` as required, the default-all vs `[]` semantics of `events` plus the 400 on unsupported events, `secret` as write-only, and `campaignId` falling back to GROWSURF_CAMPAIGN_ID. `isEnabled` is left undefined in both schema and description, so one parameter remains unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Add a webhook to your GrowSurf program" states a specific verb and resource, which cleanly separates it from the delete/update/test webhook siblings by verb alone. It stops short of explicitly naming those alternatives, so it identifies itself rather than routing by contrast.

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 concrete operational context: omit `events` to subscribe to all, send `[]` for none, and reload before retrying after a 409. It does not say when to prefer updating an existing webhook over creating another, or point at `growsurf_list_campaign_webhooks` as the pre-check for the 5-webhook cap.

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.