Skip to main content
Glama

List Library folders

list_library_folders
Read-onlyIdempotent

Browses visible child folders of the Library root or parent_folder_id. Set query to find visible folders by name across the workspace. Pass the returned next_cursor value as cursor for another page, keeping filters unchanged.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
cursorNo
page_sizeNo
parent_folder_idNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

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, non-destructive and closed-world, so safety is covered. The description adds real behavioral context beyond them: results are limited to 'visible' folders (implying permission filtering) and pagination requires echoing next_cursor while holding filters constant. It does not describe the returned item shape or ordering, which keeps it below 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?

Three short sentences, each doing distinct work: default browse behavior, query mode, and pagination. The browsing scope is front-loaded and nothing is redundant.

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?

For a 4-parameter, zero-required read tool with annotations and no output schema, the description covers the main interaction modes and pagination loop. The gaps are minor: page_size semantics and the shape of returned folder objects are unstated, though no output schema exists to cover them.

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 coverage is 0%, so the description must carry parameter meaning. It explains query (name search across the workspace), cursor (take next_cursor from the previous page), and implies parent_folder_id as the browse root, but says nothing about page_size (default 20, max 50) or the format/scope of parent_folder_id values.

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 ('Browses visible child folders of the Library root or parent_folder_id') and immediately adds the alternate mode ('Set query to find visible folders by name across the workspace'). An agent can tell the two modes apart, though it does not name a sibling such as search_library_content or get_library_folder as an alternative.

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?

Gives clear within-tool guidance: browsing via parent_folder_id versus name lookup via query, plus how to page. It never says when to choose this tool over a sibling (e.g., search_library_content or get_library_folder), so the alternative-selection guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources