GrowSurf MCP Server

Official

by growsurf

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Update Program Resource

growsurf_update_program_resource

DestructiveIdempotent

Update a GrowSurf program resource field or move it to a zero-based position; only supplied fields change, and replacement files need an upload ticket and upload result.

Instructions

Update at least one participant resource field, or move it to a zero-based position. Only supplied fields change. A replacement FILE requires a one-time uploadTicket and the unmodified uploadResult from GrowSurf's secure upload flow. API reference: https://docs.growsurf.com/developer-tools/rest-api/api-reference. Targets campaignId if supplied, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

Name	Required	Description
`url`	No	Used with `LINK`.
`text`	No	Used with `TEXT`.
`type`	No
`title`	No
`category`	No
`position`	No
`campaignId`	Yes	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.
`resourceId`	Yes
`description`	No
`isPublished`	No
`uploadResult`	No	The unmodified result returned by the secure upload flow for a replacement `FILE`.
`uploadTicket`	No	The one-time upload ticket for a replacement `FILE`.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.19.15Oct 15, 2026
- addedInput schema / properties / campaignId / minLength
```
Added value: +1
```
- changedInput schema / required
```
Previous value: -[
-  "resourceId"
-]New value: +[
+  "resourceId",
+  "campaignId"
+]
```

Changed1 schema field changedv0.19.9Oct 3, 2026

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

Addedv0.14.0Sep 10, 2026

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 openWorldHint=true, so the safety baseline is covered. The description adds genuinely useful behavior beyond that: partial-patch semantics ('Only supplied fields change'), the one-time nature of uploadTicket, the requirement that uploadResult be unmodified, and the campaignId/campaign-env fallback targeting rule.

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?

Front-loaded with the core action and patch semantics, followed by the FILE precondition and targeting rule; every sentence carries information. The bare API reference URL is the only slightly wasteful element.

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 12-parameter tool with heavy allOf/anyOf conditionals and a nested upload object, the description surfaces the two conditionals an agent most needs (at-least-one-field and FILE pairing) plus targeting. With an output schema present, return values need not be explained. Type-variant semantics (LINK/TEXT/FILE mutual exclusivity) rely on the schema, leaving a small gap.

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?

With only 42% schema description coverage, the description must compensate and largely does: it explains position is zero-based, that FILE replacement needs the paired uploadTicket+uploadResult, and that campaignId overrides GROWSURF_CAMPAIGN_ID. It still leaves type/title/category/isPublished/description semantics to the schema, so not a 5.

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 (update a program/participant resource) and adds the key scope constraint that at least one field must change or move position. It does not explicitly contrast with siblings like growsurf_create_program_resource or growsurf_prepare_program_resource_file, so a 4 rather than a 5.

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 implies when the tool applies (partial field updates and positional moves) and conditionally gates the FILE path on uploadTicket/uploadResult, but it never states when to choose this over create/delete/list resource siblings or what prerequisites (e.g., the secure upload flow) must be completed first. Usage is implied, not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server