GrowSurf

Delete Campaign Reward

growsurf_delete_campaign_reward

DestructiveIdempotent

Delete a campaign reward (reward config) from your GrowSurf program. The reward is deactivated, removed from the program's reward set, and any connected upfront-discount coupons are cleaned up. campaignRewardId is the reward key. 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": {
      "campaignRewardId": "<campaignRewardId>",
      "campaignId": "<campaignId>"
    },
    "name": "growsurf_delete_campaign_reward"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`campaignRewardId`	Yes

Output Schema

Name	Required	Description	Default
`id`	No	The deleted campaign reward id.
`success`	No	Whether the campaign reward was deleted.

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.1/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses concrete side effects an agent cannot infer: the reward is deactivated, removed from the reward set, and connected upfront-discount coupons are cleaned up. It also states the return shape { id, success }, so the agent knows the outcome is verifiable.

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 tightly packed sentences with the action front-loaded and the effects and return value following logically. The only minor waste is restating the GROWSURF_CAMPAIGN_ID fallback already present in the campaignId schema.

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 destructive two-parameter tool with an output schema and full annotation coverage, the description covers effects, targeting, and return value adequately. The remaining gap is procedural: it never says how to discover a valid campaignRewardId, which matters for a required parameter.

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 richly documented in the schema (and the description largely repeats its default), while campaignRewardId has no schema description. The one line 'campaignRewardId is the reward key' adds only marginal meaning and does not say where to source that key, so it barely compensates for the uncovered parameter.

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?

The description states a specific verb and resource ('Delete a campaign reward (reward config)') and scopes it to the GrowSurf program. It is immediately distinguishable from the sibling create/update/list reward tools because deletion and its downstream effects are spelled out.

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?

Usage is implied by the destructive verb, and targeting behavior (explicit campaignId vs GROWSURF_CAMPAIGN_ID) is covered. However, there is no explicit when-to-use guidance, no mention of using update_campaign_reward as a non-destructive alternative to deactivation, and no pointer to list_campaign_rewards to obtain the reward key.

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.