quickS3

List objects

list_objects

Read-onlyIdempotent

List objects and folders in a bucket, filtered to prefixes this access grant may read. Folders end with "/" and appear as kind "prefix".

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum objects per page (default 100)
`bucket`	Yes	Bucket name
`prefix`	No	Folder prefix to list, e.g. "reports/2026/". Omit for the bucket root.
`connectionId`	Yes	Connection ID from list_connections
`continuationToken`	No	Opaque token from a previous page

Output Schema

TableJSON Schema

Name	Required	Description	Default
`objects`	Yes
`continuationToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "continuationToken": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "objects": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "key": {
+            "type": "string"
+          },
+          "kind": {
+            "enum": [
+              "object",
+              "prefix"
+            ],
+            "type": "string"
+          },
+          "lastModified": {
+            "type": "string"
+          },
+          "size": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "key",
+          "kind",
+          "size"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "objects"
+  ],
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false, covering the safety profile. The description adds meaningful behavioral context beyond annotations: the access-grant filtering and the representation of folders as kind 'prefix' with trailing slash. These details help the agent interpret results correctly. No contradiction with annotations.

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 concise sentences with no wasted words. The primary purpose is front-loaded, and the folder representation detail is placed second. Every sentence earns its place.

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

Completeness5/5

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

Given the tool's simplicity, rich annotations, and the presence of an output schema (which covers return value details), the description is complete. It addresses access scoping and folder representation, while pagination is handled by the continuationToken parameter in the schema. Nothing critical is missing for an agent to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter is documented. The description adds value by clarifying that 'prefix' is used to list subfolders (with an example 'reports/2026/') and that folders are returned as kind 'prefix'. This helps an agent understand the semantic relationship between prefix and folder listing beyond the bare schema definitions.

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 clearly states the verb 'list' and the resource 'objects and folders in a bucket', and adds specificity about folder representation (kind 'prefix'). It is immediately distinguishable from sibling tools like list_buckets and list_connections by the explicit 'in a bucket' scope.

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 description does not explicitly mention when to use this tool versus alternatives, nor does it state any exclusions. It does include a usage constraint ('filtered to prefixes this access grant may read') which clarifies access scope, but that is about permissions, not tool selection. The purpose is clear enough that an agent might infer the appropriate tool, but explicit guidance is missing.

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

All quickS3 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?