Skip to main content
Glama

Manawa Terminal

List library items

list_library_items
Read-only

List documents in a library folder, or at the root if no folder is given.

Args:
    folder_id: Folder UUID to list (optional — omit for root-level items)
    offset: Skip this many items (default 0)
    limit: Page size (default 50, max 100)

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
folder_idNo
strategy_idNoStrategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / strategy_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Strategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.",
      +  "title": "Strategy Id"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 50,
      +  "title": "Limit",
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "title": "Offset",
      +  "type": "integer"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely useful operational detail beyond that: pagination semantics (offset skips, limit defaults to 50, max 100) and the root-listing behavior. It stops short of describing ordering or whether an empty folder errors.

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 opening sentence front-loads purpose and the root-fallback rule, and the Args block is terse with no filler. The only inefficiency is that a prose Args list duplicates what the schema already names, though it does add the default/max values.

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?

An output schema exists, so return values need not be explained. For a simple paginated read tool with strong annotations, the description covers folder scoping and paging adequately. The one real gap is the unexplained strategy_id parameter.

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 only 25% — only strategy_id is documented in the schema. The description compensates for three of the four parameters by explaining folder_id optionality and offset/limit defaults and the 100 cap. However, it completely omits strategy_id, leaving that parameter's purpose to a schema description that appears to be copy-pasted from another tool ('the card this call writes').

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 clear verb+resource ('List documents in a library folder') and clarifies root-level behavior when no folder is given, which distinguishes it from list_library_folders and get_library_item. It does not explicitly contrast with search_library, which is the nearest ambiguous sibling.

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 root-vs-folder condition is implied by the folder_id argument, giving some usage context. However, there is no explicit guidance on when to use this versus search_library or list_library_item_versions, and no prerequisites or exclusions are stated.

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