Gumloop MCP Server

Create agent

create_agent

Destructive

Create a new Gumloop agent for a user or team, attaching tools, skills, resources, and an LLM model. Requires confirmation and permission to prevent unintended account changes.

Instructions

Create a new agent. The authenticated caller must have permission to create agents on the target team. 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
`name`	No	Display name for the agent.
`tools`	No	Tools the agent can call. Each tool is an object whose shape depends on the tool type.
`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	ID of the team to create the agent under. When omitted, the agent is owned by the authenticated user.
`agent_id`	No	Optional caller-supplied agent ID. When omitted, the server generates one.
`metadata`	No	Arbitrary key/value metadata stored on the agent.
`folder_id`	No	ID of the folder to place the agent in.
`is_active`	No
`resources`	No	Resources attached to the agent.
`skill_ids`	No
`model_name`	No	ID of the LLM the agent runs on. Use `GET /models` to discover valid values.
`description`	No
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`system_prompt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv3.0.0Oct 5, 2026

addedInput schema / $defs / is_active

Added value: +{
+  "default": true,
+  "description": "Whether the agent is active. Defaults to `true`.\n\nSetting this to `false` retires the agent: it disappears from `GET /agents`, and `GET`/`PATCH /agents/{agent_id}` return `404`, so it cannot be reactivated through the API. This is not a pause switch — to stop an agent from running while keeping it reachable, disable its triggers instead.\n",
+  "type": "boolean"
+}

addedInput schema / $defs / skill_ids

Added value: +{
+  "description": "IDs of skills to attach to the agent. Attachment happens inside the create transaction, so an invalid ID fails the whole request (no orphaned agent). Omit to attach none. The caller must hold `INVOKE` on each skill. After creation, manage skills with `PATCH /agents/{agent_id}/skills`.\n",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

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 / is_active / $ref
```
Added value: +"#/$defs/is_active"
```
removedInput schema / properties / is_active / default
```
Removed value: -true
```

removedInput schema / properties / is_active / description

Removed value: -"Whether the agent is active. Defaults to `true`.\n\nSetting this to `false` retires the agent: it disappears from `GET /agents`, and `GET`/`PATCH /agents/{agent_id}` return `404`, so it cannot be reactivated through the API. This is not a pause switch — to stop an agent from running while keeping it reachable, disable its triggers instead.\n"

removedInput schema / properties / is_active / type
```
Removed value: -"boolean"
```
addedInput schema / properties / payload / properties / is_active / $ref
```
Added value: +"#/$defs/is_active"
```
removedInput schema / properties / payload / properties / is_active / default
```
Removed value: -true
```

removedInput schema / properties / payload / properties / is_active / description

Removed value: -"Whether the agent is active. Defaults to `true`.\n\nSetting this to `false` retires the agent: it disappears from `GET /agents`, and `GET`/`PATCH /agents/{agent_id}` return `404`, so it cannot be reactivated through the API. This is not a pause switch — to stop an agent from running while keeping it reachable, disable its triggers instead.\n"

removedInput schema / properties / payload / properties / is_active / type
```
Removed value: -"boolean"
```
addedInput schema / properties / payload / properties / skill_ids / $ref
```
Added value: +"#/$defs/skill_ids"
```

removedInput schema / properties / payload / properties / skill_ids / description

Removed value: -"IDs of skills to attach to the agent. Attachment happens inside the create transaction, so an invalid ID fails the whole request (no orphaned agent). Omit to attach none. The caller must hold `INVOKE` on each skill. After creation, manage skills with `PATCH /agents/{agent_id}/skills`.\n"

removedInput schema / properties / payload / properties / skill_ids / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / payload / properties / skill_ids / type
```
Removed value: -[
-  "array",
-  "null"
-]
```
addedInput schema / properties / skill_ids / $ref
```
Added value: +"#/$defs/skill_ids"
```

removedInput schema / properties / skill_ids / description

Removed value: -"IDs of skills to attach to the agent. Attachment happens inside the create transaction, so an invalid ID fails the whole request (no orphaned agent). Omit to attach none. The caller must hold `INVOKE` on each skill. After creation, manage skills with `PATCH /agents/{agent_id}/skills`.\n"

removedInput schema / properties / skill_ids / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / skill_ids / type
```
Removed value: -[
-  "array",
-  "null"
-]
```

First observedv2.0.1Oct 3, 2026

TDQS

A3.6/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, so the safety profile is partly covered. The description adds value beyond them by naming the permission requirement, mandating explicit confirmation, warning that runs can spend credits or trigger downstream actions, and advising against automatic resubmission of unknown outcomes.

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?

Purpose is front-loaded in the first sentence, followed by concise preconditions and warnings. The closing sentence about runs spending credits is slightly tangential to a create operation, but it remains short and relevant as a caution.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter, nested-object mutation with no output schema, the description covers permissions, confirmation, and side effects but omits how to reconcile the body-flag parameters versus the payload/payload_file alternatives and gives no sense of the return value. Adequate but with clear gaps where the schema is expected to carry the load.

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?

With 75% schema description coverage across 16 parameters, the schema itself is the primary source of field semantics, including the detailed is_active and skill_ids behaviors. The description contributes nothing about individual parameters except the confirm gate, so the baseline 3 is appropriate.

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+resource ('Create a new agent'), which is unambiguous on its own. However, it never distinguishes itself from sibling mutation tools such as update_agent, so the agent must rely on the name alone to know this is creation rather than modification.

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 supplies a real precondition ('caller must have permission to create agents on the target team') and a confirmation gate ('Explicit confirmation is required for this exact account operation'), which implies usage conditions. It does not, however, state when to prefer this over alternatives or any when-not-to-use cases.

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

Deploy Server

Create agent

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools