Skip to main content
Glama

Move items to a folder

driftnet_move_items
Idempotent

Move one or more saved items into a specified folder in your reader tree when they were sorted into the wrong one. Returns an undo id so the move can be reverted.

Instructions

File one or more items into a folder of the reader's tree, e.g. when they were sorted into the wrong one. To reorganise the whole tree use driftnet_suggest_folders; to star, note or trash an item use driftnet_update_item. ids: repeated ids count once, and items already in the target folder are left as they are. The batch is all-or-nothing: if any id or the folder is unknown, nothing moves and the error names it. folder is a folder id from driftnet_list_folders, not its display name. The placement counts as the reader's own choice, so automatic sorting will never move these items again. Returns an undo id for driftnet_undo_move.

Input Schema

NameRequiredDescriptionDefault
idsYesItem ids to move together, 1–500 positive integers, e.g. [42, 43]
folderYesTarget folder id from driftnet_list_folders, e.g. 'coding'

Output Schema

NameRequiredDescriptionDefault
undoYes
countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.9/5.0
Behavior5/5

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

The description goes well beyond the annotations by explaining idempotent handling of repeated ids, leaving already-placed items unchanged, all-or-nothing batch semantics, error behavior for unknown ids or folders, and the lasting effect on automatic sorting. It also notes that the call returns an undo id for driftnet_undo_move, which is key operational context.

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 dense but front-loaded: the core action comes first, followed by routing guidance, batch semantics, folder id requirements, side effects, and return value. Every sentence adds operational value without unnecessary repetition.

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?

Despite the tool having an output schema and annotations, the description supplies the important behavioral details an agent needs: batch atomicity, idempotency around duplicate and already-moved items, folder-id usage, sorting side effects, and undo support. Nothing essential is missing.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema: repeated ids are counted once, already-targeted items are left alone, the whole batch fails atomically if any id or folder is unknown, and folder must be an id rather than a display name.

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: 'File one or more items into a folder of the reader's tree.' It distinguishes this operation from sibling tools by naming the alternatives for whole-tree reorganisation and for starring, noting, or trashing items.

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?

It states the primary use case ('when they were sorted into the wrong one') and explicitly routes other tasks to driftnet_suggest_folders and driftnet_update_item. This leaves little ambiguity about when to invoke this tool versus its siblings.

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