Tokenrip

List artifacts

artifact_list

Read-onlyIdempotent

List owned or team artifacts with complete offset continuation. Follow nextCursor as offset; stable collections are ordered updatedAt descending then ID descending.

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": "artifact_list"
  }
}

Input Schema

Name	Required	Description
`team`	No	The artifacts shared with this team (slug or id). Not with workspaceId.
`type`	No	Only artifacts of this type.
`limit`	No	At most this many, 1 to 100.
`since`	No	Only what happened since: an ISO 8601 timestamp, or a number of days back (7 = the last week).
`folder`	No	Only the artifacts in this folder: an id, or a slug (in workspaceId, else in team, else your personal folders).
`offset`	No	Where the page starts: the previous page's nextCursor.
`unfiled`	No	Only the artifacts in no folder.
`workspaceId`	No	The artifacts you can read in this workspace (its id or its slug). Not with team.

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"
-}
```

Changed3 schema fields changedOct 27, 2026

addedOutput schema / properties / items / items / properties / currentVersionNumber

Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

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

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "from": {
+          "enum": [
+            "file",
+            "folder",
+            "workspace",
+            "default"
+          ],
+          "type": "string"
+        },
+        "value": {
+          "anyOf": [
+            {
+              "enum": [
+                "off",
+                "all"
+              ],
+              "type": "string"
+            },
+            {
+              "maximum": 100,
+              "minimum": 1,
+              "type": "integer"
+            }
+          ]
+        }
+      },
+      "required": [
+        "value",
+        "from"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "url",
-  "rawUrl",
-  "type",
-  "currentVersionId",
-  "alias",
-  "title",
-  "folder",
-  "visibility",
-  "mimeType",
-  "sizeBytes",
-  "versionCount",
-  "ownerId",
-  "parentArtifactId",
-  "publicAsset",
-  "createdAt",
-  "updatedAt"
-]New value: +[
+  "id",
+  "url",
+  "rawUrl",
+  "type",
+  "currentVersionId",
+  "alias",
+  "title",
+  "folder",
+  "visibility",
+  "mimeType",
+  "sizeBytes",
+  "versionCount",
+  "currentVersionNumber",
+  "ownerId",
+  "parentArtifactId",
+  "publicAsset",
+  "history",
+  "createdAt",
+  "updatedAt"
+]

Changed3 schema fields changedOct 27, 2026

addedOutput schema / properties / items / items / properties / folder

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "id": {
+          "format": "uuid",
+          "pattern": "^([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)$",
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        },
+        "teamSlug": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "slug"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / items / items / properties / rawUrl

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "url",
-  "type",
-  "currentVersionId",
-  "visibility",
-  "alias",
-  "title",
-  "mimeType",
-  "sizeBytes",
-  "versionCount",
-  "ownerId",
-  "parentArtifactId",
-  "publicAsset",
-  "createdAt",
-  "updatedAt"
-]New value: +[
+  "id",
+  "url",
+  "rawUrl",
+  "type",
+  "currentVersionId",
+  "alias",
+  "title",
+  "folder",
+  "visibility",
+  "mimeType",
+  "sizeBytes",
+  "versionCount",
+  "ownerId",
+  "parentArtifactId",
+  "publicAsset",
+  "createdAt",
+  "updatedAt"
+]

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"The artifacts of this workspace you can read. Not with team."New value: +"The artifacts you can read in this workspace (its id or its slug). Not with team."

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description contributes genuinely new behavior: offset-style cursor continuation and a deterministic sort (updatedAt descending, then ID descending) that makes pagination stable. It does not mention permission scope or whether results include trashed items, which keeps it off 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.

Conciseness5/5

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

Two sentences, no waste, with the pagination contract front-loaded before the ordering guarantee. Every clause carries information an agent would otherwise have to discover by experiment.

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 an output schema present, return-shape explanation is unnecessary and correctly omitted, and the pagination/ordering details are the main thing an agent needs for a list tool. The remaining gap is scope semantics across the team, workspaceId and personal-folder options, which the description never reconciles.

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 description coverage is 100%, so all eight parameters already carry meaning and the baseline is 3. The description's ordering and cursor notes reinforce the offset parameter but do not explain the scope parameters (team vs. workspaceId) or the since/folder interplay beyond what the schema states.

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 and resource ("List owned or team artifacts") and adds a scope qualifier, so an agent knows it enumerates rather than fetches. It stops short of naming how it differs from sibling listers such as trash_list or output_list, and the scope phrase omits the workspaceId case that the schema supports.

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?

The usage guidance that exists is about mechanics (follow nextCursor as offset), not about tool selection. Nothing tells the agent when to reach for this versus artifact_get or a filtered search, and no exclusions or prerequisites are given. Usage is implied by the 'List' verb rather than stated.

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.