Atwork

Update Folder

folder.update

DestructiveIdempotent

Rename a folder, change its icon or description, or move it inside another folder of the same space. Only the settings you name change. Ids come from workspace.structure.

Input Schema

Name	Required	Description
`icon`	No
`name`	No
`spaceId`	Yes	The space the folder is in
`folderId`	Yes
`description`	No
`parentFolderId`	No	Move the folder inside another folder of the same space

Output Schema

Name	Required	Description
`name`	Yes
`changed`	Yes
`folderId`	Yes
`location`	Yes	Where the folder now sits

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 4, 2026
- removedOutput schema / properties / location / properties / folderId / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / location / properties / folderId / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / location / properties / folderName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / location / properties / folderName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedOct 27, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already declare this as destructive, idempotent, and not open-world. The description adds meaningful behavior beyond them: only named settings change, and moves are constrained to another folder in the same space.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences are front-loaded with the main capabilities, partial-update semantics, and ID prerequisite. There is no redundant wording.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description is nearly complete for a folder mutation, though it could mention permission requirements or child-folder effects when moving.

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?

The description names the main updatable fields and explains that parentFolderId moves the folder within the same space. With only 33% schema description coverage, it does not fully compensate for undocumented parameters like folderId or clarify all ID sources.

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 uses a specific verb and resource: rename a folder, change icon or description, or move it into another folder. It clearly distinguishes this partial-update operation from sibling tools like folder.create, folder.delete, and item_tree.move.

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 states the update scope and that IDs come from workspace.structure, which is useful prerequisite context. However, it does not explicitly compare this tool with alternatives such as item_tree.move or explain when not to use folder.update.

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

All Atwork 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.

Resources

Need Help?