Skip to main content
Glama

Manawa Terminal

Move library folder

move_library_folder

Move a library folder under a different parent (or to root).

Args:
    folder_id: The folder UUID to move
    parent_id: New parent folder UUID (omit / null for library root)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "folder_id": "<folder_id>"
    },
    "name": "move_library_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idYes
parent_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. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation and safety profile are covered for free. The description adds only that the target is a parent folder or library root. It does not disclose permission requirements, what happens to nested child folders or items, or whether the move can create cycles.

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 summary is front-loaded in a single sentence and the Args block is compact and scannable. The docstring formatting is slightly redundant with the schema, but nothing is padded or wasted.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. For a two-field move operation the description covers the input semantics and root-targeting case; the only residual gap is the orphaned strategy_id parameter, which is a schema defect more than a description omission.

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 33%, so the schema leaves folder_id and parent_id undocumented and the description compensates by defining both, including the omit-or-null convention for library root. However, the third parameter strategy_id is wholly unaddressed by the description, and its schema text ('the card this call writes keeps that id') reads as copied from an unrelated tool, leaving that parameter semantically murky for a folder move.

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?

The first sentence gives a specific verb and resource: 'Move a library folder under a different parent (or to root).' This clearly separates it from sibling mutations like move_library_item, rename_library_folder, and delete_library_folder. It does not explicitly name those siblings, but the verb-plus-resource pairing is unambiguous.

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 parenthetical '(or to root)' implies the two usage modes: reparenting versus resetting to the library root, and the Args section reinforces that parent_id may be omitted. However, it gives no guidance on when to choose move_library_folder instead of delete/create or move_library_item, and it states no prerequisites or exclusions.

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