Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Delete Webhook

growsurf_delete_campaign_webhook
DestructiveIdempotent

Remove a webhook from a GrowSurf program by ID, returning the webhook ID and success status. Use it to clean up or disable webhook notifications for a specific campaign.

Instructions

Remove a webhook from your GrowSurf program by id. Returns { id, success }. 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_delete_campaign_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
idNoId of the webhook that was deleted.
successNoWhether the webhook was deleted.

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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return payload ({ id, success }) and the campaign-resolution behavior. It stops short of saying the deletion is permanent, whether in-flight deliveries are affected, or what permission scope is needed.

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?

Two short sentences: the action and return shape come first, followed by the targeting rule. No filler, no restatement of the title, and every clause carries actionable information.

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?

An output schema exists and annotations carry the destructive/idempotent profile, so the description is nearly complete for a simple two-parameter delete. The remaining gap is the source of webhookId and the mismatch between 'omitted campaignId' and the schema's required list, which could cause a malformed call.

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 50%: campaignId is well documented in the schema, and the description reinforces its fallback behavior, but webhookId has no description anywhere and the text only says 'by id' without stating where that id comes from (presumably growsurf_list_campaign_webhooks). Added meaning is real but partial for a 2-parameter tool.

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?

States a specific verb and resource ('Remove a webhook from your GrowSurf program by id') and names the return shape, so the agent knows exactly what the call does. It does not explicitly contrast with the update/create/test webhook siblings, but the delete framing is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the campaign-targeting rule (explicit campaignId vs the GROWSURF_CAMPAIGN_ID fallback), which is real usage guidance. It never says when to prefer this over growsurf_update_campaign_webhook or that the webhookId should come from growsurf_list_campaign_webhooks, and it says campaignId can be omitted even though the schema marks it required — a confusing inconsistency for the caller.

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