Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Cancel Delayed Referral

growsurf_cancel_delayed_referral
DestructiveIdempotent

Cancel a participant's pending delayed referral trigger before the delay elapses, such as on a refund or cancellation. Returns success or indicates no pending trigger.

Instructions

Cancel a pending delayed referral trigger for a participant before the delay elapses (e.g. on refund/cancellation). Returns { success, message }; success is false when the participant has no pending delayed trigger. Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

NameRequiredDescriptionDefault
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.
participantIdNo
participantEmailNo

Output Schema

NameRequiredDescriptionDefault
messageNoHuman-readable result message. Present when credit was not awarded immediately.
successNoWhether referral credit was awarded, scheduled, or cancelled.

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
    • addedInput schema / required
      Added value: +[
      +  "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?

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is supplied. The description adds real value beyond them by disclosing the return shape and, more importantly, the no-op condition: `success` is false when there is no pending delayed trigger. It doesn't say what permissions are needed or whether the participant record itself is affected.

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 compact clauses: what it does, when it's used, and what comes back on failure. The scope and failure condition are front-loaded; nothing is padding.

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?

With annotations covering the destructive and idempotent profile and an output schema present, the description only needs to add the non-obvious semantics — which it does via the failure condition. The remaining gap is the participant identifier pair, left unexplained for a 3-parameter mutation tool.

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%, with participantId and participantEmail entirely undocumented, and the description does not compensate — it never says which identifier wins if both are supplied or what happens on an ambiguous email. The campaignId fallback it mentions is already stated in the schema description, so that sentence adds no new meaning.

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?

The description states a specific verb and object — cancel a *pending delayed* referral trigger for a participant — with the temporal constraint 'before the delay elapses' that distinguishes it from a general trigger tool. It stops short of naming a sibling, so the differentiation is inferred rather than explicit.

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?

It gives one concrete usage occasion ('e.g. on refund/cancellation'), which implies when to reach for it. It offers no when-not guidance and no explicit contrast with the trigger-related siblings, so an agent must infer the boundary.

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