Gumloop MCP Server

Create skill

create_skill

Destructive

Upload a skill package containing a SKILL.md file to create a new skill, automatically generating its initial version.

Instructions

Upload a skill package and create a new skill. The package must include a SKILL.md with name and description frontmatter; uploads may be a single .md file (stored as SKILL.md), or a .zip / .skill archive containing SKILL.md at its root. The initial version is created automatically. Maximum upload size is 10 MB. Explicit confirmation is required for this exact account operation. Runs can spend credits or trigger downstream actions; never resubmit unknown outcomes automatically.

Input Schema

TableJSON Schema

Name	Required	Description
`files`	No
`account`	No	Named private Gumloop account; selects private credentials and user/team identity.
`confirm`	No	Set true only when the user asked for exactly this action.
`payload`	No	Complete JSON request body instead of body flags. Preserves current endpoint fields and values.
`team_id`	No	Team that should own the skill. When omitted, the skill is owned by the authenticated user.
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv3.0.0Oct 5, 2026

addedInput schema / $defs / files

Added value: +{
+  "description": "Regular local file paths, not base64; each file and total upload at most 5 MiB. Paths cannot be symlinks.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 25,
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / properties / confirm / description

Previous value: -"Must be true for this exact requested account change, agent/flow execution, upload or deletion."New value: +"Set true only when the user asked for exactly this action."

addedInput schema / properties / files / $ref
```
Added value: +"#/$defs/files"
```

removedInput schema / properties / files / description

Removed value: -"Regular local file paths, not base64; each file and total upload at most 5 MiB. Paths cannot be symlinks."

removedInput schema / properties / files / items

Removed value: -{
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / files / maxItems
```
Removed value: -25
```
removedInput schema / properties / files / minItems
```
Removed value: -1
```
removedInput schema / properties / files / type
```
Removed value: -"array"
```
addedInput schema / properties / payload / properties / files / $ref
```
Added value: +"#/$defs/files"
```

removedInput schema / properties / payload / properties / files / description

Removed value: -"Regular local file paths, not base64; each file and total upload at most 5 MiB. Paths cannot be symlinks."

removedInput schema / properties / payload / properties / files / items
```
Removed value: -{
-  "minLength": 1,
-  "type": "string"
-}
```
removedInput schema / properties / payload / properties / files / maxItems
```
Removed value: -25
```
removedInput schema / properties / payload / properties / files / minItems
```
Removed value: -1
```
removedInput schema / properties / payload / properties / files / type
```
Removed value: -"array"
```

First observedv2.0.1Oct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true; the description goes further by disclosing credit spend, downstream side effects, and the mandatory confirmation gate. That is real value beyond the annotations, though it contains a size figure that conflicts with the schema (see below).

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 packaging rules, then the safety/confirmation note. The second paragraph overlaps with the confirm parameter's own description, but overall it earns its length.

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 no output schema and 6 parameters (none required), the description adequately covers the packaging contract, confirmation requirement, and side-effect risk. The size contradiction and unaddressed body flags (payload/payload_file/account/team_id) are the remaining gaps.

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 83% (baseline 3) and the description does add useful non-schema constraints: SKILL.md with name/description frontmatter, accepted .md/.zip/.skill forms, archive layout. However, it never explains the confirm, account, team_id, or payload_file parameters, and its stated 'Maximum upload size is 10 MB' contradicts the schema's 'at most 5 MiB' per file/total, which could cause failed uploads.

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?

Specific verb+resource ('Upload a skill package and create a new skill') plus the packaging constraints that define what this operation actually consumes. It is trivially distinguishable from siblings like update_skill, delete_skill, and upload_file.

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?

States the confirmation prerequisite and the 'never resubmit unknown outcomes' rule, which is genuinely actionable guidance. It does not explicitly route against alternatives such as update_skill or a plain file upload, so it falls short of a 5.

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

Deploy Server

Create skill

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools