TeamShared

storage_list

List active Storage objects in the caller's org, newest first.

Each row is metadata plus download_url (bearer GET /v1/drive/{id}/content). Published objects also include a fresh signed_url (presigned bucket GET, primary for agents) plus signed_url_expires_in / signed_url_expires_at, and durable share_url / public_url (/d/{share_token}, console/human fallback). /d/{token} is Storage's public raw-bytes route. Pass work_id or project_id to list attachments (project_id wins if both are set; folder filters are ignored on those joins). Pass parent_id / folder_id to list one folder (root = org root). Omit both to list every active object. Folders sort first. Archived objects stay joined but are omitted. work_id / project_id list every Storage join (blobs and document-capable objects). Transcripts stay on file_list(work_id=). drive_list is a deprecated alias of this tool.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	Optional case-insensitive title substring
`work_id`	No	Only Storage objects attached to this work item UUID
`folder_id`	No	Alias of parent_id
`parent_id`	No	Folder UUID to list, or 'root' / empty for the org root. Omit to list everything.
`project_id`	No	Only Storage objects attached to this project UUID

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 5, 2026

addedInput schema / properties / folder_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Alias of parent_id"
+}

addedInput schema / properties / parent_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Folder UUID to list, or 'root' / empty for the org root. Omit to list everything."
+}

AddedSep 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description carries the full burden, and it delivers: sorting (newest first, folders first), archived-object omission, URL semantics for download_url/signed_url/share_url/public_url, route details, and parameter precedence. This goes well beyond the schema and gives a complete behavioral picture.

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?

The description is long and dense, but nearly every sentence carries operational value: filtering modes, URL semantics, exclusions, and sibling routing. It is front-loaded with the core purpose and organized by behavior, though it could be slightly tightened without losing information.

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 complexity and the presence of an output schema, the description is remarkably complete: it covers output row composition, authentication-bearing URLs, filter modes, precedence, exclusions, and deprecated aliases. An agent has everything needed to call this tool correctly.

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

Parameters5/5

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

Schema coverage is already high at 83%, but the description adds significant meaning beyond the schema: it explains that folder filters are ignored on work/project joins, that 'root' means org root, and how the URL fields relate to each other. This materially improves parameter understanding.

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 opens with a precise verb+resource: 'List active Storage objects in the caller's org, newest first.' It also distinguishes itself from related tools by noting that drive_list is a deprecated alias and that transcripts belong on file_list, so an agent can tell it apart from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit filter-mode guidance: pass work_id/project_id for attachments, pass parent_id/folder_id for a single folder, or omit both to list everything. It also states precedence ('project_id wins if both are set') and points to file_list for transcripts, making when-to-use and alternatives clear.

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

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