Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Send Test Webhook

growsurf_test_campaign_webhook
Destructive

Send a live test event to a GrowSurf campaign webhook and return the mock payload plus the endpoint response. Optionally choose the event type to simulate.

Instructions

Send a live test event to a webhook on your GrowSurf program using its stored URL and secret. Optionally pass event to choose which event type to simulate; when omitted, the webhook's first enabled event is used (returns 400 if the webhook has no enabled events). Returns the mock payload and the receiving endpoint's response. 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": {
      "webhookId": "<webhookId>",
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_test_campaign_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventNo
webhookIdYes
campaignIdYesTarget 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.

Output Schema

NameRequiredDescriptionDefault
payloadNoThe mock event payload that was sent.
successNoWhether the test webhook request completed.
responseNoResponse returned by the webhook endpoint during the test.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.33
    • 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."
  2. Changed2 schema fields changedv0.19.15
    • addedInput schema / properties / campaignId / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
      -  "webhookId"
      -]New value: +[
      +  "webhookId",
      +  "campaignId"
      +]
  3. Changed1 schema field changedv0.19.9
    • changedInput schema / properties / campaignId / description
      Previous value: -"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Pass the `id` returned by growsurf_create_campaign to configure or operate a program you just created, without restarting the server."New 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."
  4. First observedv0.12.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so safety profile is covered; the description still adds real value by disclosing that the call dispatches to the customer's endpoint with stored credentials, returns the mock payload plus the receiving endpoint's response, and errors with 400 when no enabled event exists. It does not spell out what 'live' means for side effects on the receiving side, leaving some ambiguity against the destructive hint.

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?

Three dense sentences, front-loaded with the action and its external effect, followed by parameter defaults and error behavior. Slight redundancy in restating the GROWSURF_CAMPAIGN_ID fallback that the schema already documents, but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, side-effecting tool with an output schema, the description covers the action, external dispatch, defaults, and the main error case, so an agent could invoke it correctly. The residual gap is provenance for the required webhookId and a note on whether the test can affect the receiving system, which matters given destructiveHint=true.

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 coverage is only 33%, and the description compensates only partially: it explains event's optionality and fallback (first enabled event, 400 if none) and repeats the campaignId env fallback already documented in the schema. It says nothing about where webhookId comes from (presumably growsurf_list_campaign_webhooks) or what the enum choices represent, leaving the required ID and the enum values unexplained outside the schema.

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 specific verb and resource: sending a live test event to a webhook on a GrowSurf program, using the webhook's stored URL and secret. This is clearly distinguishable from the CRUD siblings (create/delete/update_campaign_webhook) and from list_campaign_webhooks, since the action is simulation, not configuration.

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 framing ('live test event', 'using its stored URL and secret') makes the use case — verifying a webhook endpoint without manual setup — clear, and it documents the failing case (400 when the webhook has no enabled events). It stops short of naming exclusions or alternatives, but no sibling appears to offer an overlapping capability.

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