GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create Program Resource

growsurf_create_program_resource

Create FILE, LINK, or TEXT resources for GrowSurf campaign participants; new resources default to draft unless set to published.

Instructions

Create a FILE, LINK, or TEXT resource for participants. LINK requires an HTTPS url. TEXT requires plain text. A FILE up to 10 MB requires a one-time uploadTicket and the unmodified uploadResult from GrowSurf's secure upload flow. New resources default to draft unless isPublished is set. API reference: https://growsurf.com/openapi.json. Targets campaignId if supplied, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

Name	Required	Description
`url`	No	Used only with `LINK`.
`text`	No	Used only with `TEXT`.
`type`	Yes
`title`	Yes
`category`	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.
`description`	No
`isPublished`	No
`uploadResult`	No	The unmodified result returned by the secure upload flow. Used only with `FILE`.
`uploadTicket`	No	The one-time upload ticket. Used only with `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: -[
-  "type",
-  "title"
-]New value: +[
+  "type",
+  "title",
+  "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

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds genuinely non-obvious behavior: new resources default to draft unless `isPublished` is set, files are capped at 10 MB, and the upload ticket is single-use, which reinforces the non-idempotent hint. It does not mention permission or auth requirements, so it stops short of a 5.

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?

Five tight sentences, front-loaded with the resource types and their constraints, followed by default behavior and targeting logic. The closing API reference URL is the only line that does not directly help an agent decide or invoke, keeping it just short of a 5.

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 10-parameter tool with conditional allOf constraints, a nested uploadResult object, and an output schema, the description covers the decision-critical parts: type selection, per-type required payloads, size limit, publish default, and campaign targeting. The remaining gap is the absence of any mention of the prerequisite upload tool that issues the ticket, which an agent would need to chain calls correctly.

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?

Schema description coverage is only 50%, so the description has to compensate, and it does for the hard parameters: `type`-conditional requirements, the one-time nature of `uploadTicket`, the requirement that `uploadResult` be unmodified, the `isPublished` draft default, and `campaignId` falling back to GROWSURF_CAMPAIGN_ID. `title`, `category`, and `description` are left entirely to the schema, but their names are largely self-explanatory.

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 opens with a specific verb and resource: 'Create a `FILE`, `LINK`, or `TEXT` resource for participants.' The three supported resource variants are enumerated, which distinguishes this clearly from siblings like growsurf_update_program_resource, growsurf_delete_program_resource, and growsurf_list_program_resources.

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?

It states the per-type prerequisites explicitly: `LINK` needs an HTTPS url, `TEXT` needs plain text, and `FILE` needs a one-time `uploadTicket` plus the unmodified `uploadResult` from the secure upload flow. That gives strong when-to-use context, but it never names the sibling tool that produces the upload ticket (growsurf_prepare_program_resource_file) nor says when to prefer update_program_resource over creating a new resource.

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

Deploy Server