Tokenrip

List folders

folder_list

Read-onlyIdempotent

List your personal folders, a team's (team), or the ones you can see in a workspace (workspaceId). Follow nextCursor until null for the complete collection; pages are ordered by folder ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "folder_list"
  }
}

Input Schema

Name	Required	Description
`team`	No	List this team's folders (slug or id).
`limit`	No
`cursor`	No
`workspaceId`	No	List the folders you can see in this workspace (its id or its slug).

Output Schema

Name	Required	Description	Default
`items`	Yes
`partial`	Yes
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 12, 2026
- removedOutput schema / properties / items / items / properties / audience
```
Removed value: -{
-  "enum": [
-    "internal",
-    "shared"
-  ],
-  "type": "string"
-}
```

Changed2 schema fields changedOct 27, 2026

addedOutput schema / properties / items / items / properties / history

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "enum": [
+            "off",
+            "all"
+          ],
+          "type": "string"
+        },
+        {
+          "maximum": 100,
+          "minimum": 1,
+          "type": "integer"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "slug",
-  "owner_id",
-  "team_id",
-  "artifact_count",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "id",
+  "slug",
+  "owner_id",
+  "team_id",
+  "artifact_count",
+  "history",
+  "created_at",
+  "updated_at"
+]

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"List the folders you can see in this workspace."New value: +"List the folders you can see in this workspace (its id or its slug)."

removedInput schema / properties / workspaceId / format
```
Removed value: -"uuid"
```
addedInput schema / properties / workspaceId / maxLength
```
Added value: +64
```
addedInput schema / properties / workspaceId / minLength
```
Added value: +1
```

removedInput schema / properties / workspaceId / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: pagination must be looped until `nextCursor` is null and pages are ordered by folder ID, which is not derivable from annotations or schema.

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?

Two tight sentences: scope selection front-loaded, pagination behavior second. No filler, no restatement of the title, and every clause carries usable information.

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-value explanation is unnecessary, and the description covers the two things an agent most needs: scope selection and pagination termination. It doesn't state whether `team` and `workspaceId` are mutually exclusive or how they combine, which is the remaining ambiguity for a 4-parameter list tool.

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 only 50% schema coverage, `team` and `workspaceId` are documented in the schema, and the description restates their scoping meaning without adding format detail. It does address the undocumented `cursor` parameter by explaining the follow-until-null loop, but `limit` receives no mention anywhere, leaving a real gap.

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?

The description gives a specific verb (list) and resource (folders) and enumerates the three scopes: personal, a team's via `team`, and a workspace's via `workspaceId`. It never explicitly contrasts itself with siblings like `workspace_list` or `team_list`, so an agent must infer the boundary from the resource name alone.

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?

Usage is clearly implied: pick the parameter matching the scope you want to enumerate, with no parameters meaning personal folders. The pagination instruction ('Follow nextCursor until null') is concrete procedural guidance, but there is no statement of when-not to use it or which sibling to prefer for adjacent resources.

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

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