Skip to main content
Glama

reorder_folders

Assign each folder ID a position to set a custom folder sequence, helping you organize Instapaper folders to match your workflow.

Instructions

Reorder your folders in a custom sequence. Provide an array of folder IDs with their desired positions. This helps organize your folder structure for better workflow.

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_order": "<folder_order>"
    },
    "name": "reorder_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_orderYesArray of folder ID and position pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It implies a mutation operation by saying 'reorder', but it does not explain permissions, whether the operation is destructive to existing ordering, what happens to folders omitted from the array, whether duplicate positions are allowed, or what the result looks like. The description is too thin for a mutation tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the action and parameter shape, but the final sentence about better workflow is generic filler that does not help invocation. It is short enough to scan, but it spends a sentence on vague benefits rather than behavioral detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mutation tool with one required parameter, no output schema, and no annotations. The description should therefore explain the reorder semantics more fully: whether the supplied order is partial or complete, what happens to unmentioned folders, and whether positions are absolute or relative. Those gaps are significant for a tool that changes folder structure.

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 100%, so the schema already documents folder_order, folder_id, and position. The description restates that the array contains folder IDs with desired positions but adds no further semantics such as whether positions must be contiguous, whether all folders must be listed, or how conflicts are resolved. Baseline 3 is appropriate because the schema carries the parameter documentation.

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 description clearly states the specific verb and resource: reorder folders into a custom sequence. It is distinguishable from sibling folder operations like create_folder, delete_folder, and list_folders because it describes changing ordering rather than creation, deletion, or listing. It does not explicitly contrast itself with those siblings, so it is not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is that providing folder IDs and positions helps organize folder structure for workflow. There is no explicit when-to-use context, no alternatives, no prerequisites, and no warnings about whether all folders must be included or how omitted folders are handled. This is implied usage at best.

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