Mark

List Asset Folders

list_asset_folders

Read-onlyIdempotent

Lists the Google Drive folders that hold at least one synced asset, as paths like "Brand Assets/Campaigns/Winter push", sorted. A parent folder holding only subfolders appears only inside its children's paths. Pass a path as search_assets folder to get the assets in it and its subfolders. Lists at most 2,000; capped is true when there are more. Does not change anything. Related: search_assets.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`capped`	Yes
`folders`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to carry the full safety burden. It adds useful behavioral context beyond annotations: sorted paths, parent-folder omission behavior, and the 2,000-result cap with capped=true.

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?

The description is compact and front-loaded, immediately stating what is listed and in what format. Every sentence adds useful information about path behavior, result caps, or the related search_assets workflow.

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 empty input schema, rich annotations, and existing output schema, the description is complete enough for an agent to call this tool correctly. It covers the key caveats an agent needs: path construction, parent-only folder visibility, result limits, and the capped indicator.

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?

This tool takes no parameters, so the baseline is 4. The description does not need to explain input semantics, and it appropriately focuses on output behavior and how returned paths feed into search_assets.

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: it lists Google Drive folders containing synced assets, with path formatting and sorting. It clearly distinguishes this folder-discovery action from asset retrieval by pointing to search_assets for the next step.

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?

It gives clear usage context by explaining that a returned path can be passed as the search_assets folder to retrieve assets within it. The related search_assets tool is named, though there is no explicit when-not-to-use guidance.

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

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