Skip to main content
Glama
Sign In
PikoReels MCP

PikoReels MCP

by Honey2339
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Move media into a folder

move_uploads_to_folder

Move library media into a folder or out of all folders by passing folderId null. Updates metadata only; no files are re-uploaded or changed.

Instructions

Move library media into a folder, or out of every folder by passing folderId as null. Moves are metadata only — nothing is re-uploaded and no file changes.

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": {
      "uploadIds": "<uploadIds>",
      "folderId": "<folderId>"
    },
    "name": "move_uploads_to_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderIdYesDestination folder id, or null to move them out of any folder.
uploadIdsYesUpload ids from list_library_uploads.
workspaceIdNoWorkspace to act in. Defaults to the active one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, and the description usefully adds that moves are metadata-only with no re-upload or file changes — meaningful reassurance for a mutation. It stops short of covering failure modes (nonexistent folder, invalid upload ids) or permission requirements.

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?

Two tight sentences, front-loaded with the primary action and immediately followed by the non-obvious null case. No filler or repetition of the title.

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 3-parameter metadata mutation with full schema coverage and annotations, the description covers the essential behavior and the null sentinel. With no output schema, it could say more about what a successful move returns, but nothing needed to invoke the tool correctly is missing.

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 all three parameters are already documented in the schema, including folderId's null semantics and uploadIds sourcing from list_library_uploads. The description adds no syntax or format detail beyond that, making the baseline 3 correct.

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?

States a specific verb (move), resource (library media), and destination (a folder), plus the inverse case (out of every folder via folderId=null). This is unambiguous against siblings like list_library_uploads, delete_upload, and create_folder.

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 null-folderId branch is explained, which implies the two modes of use, but there is no explicit guidance on when to prefer this over alternatives (e.g. delete_upload or create_folder) or any prerequisites such as needing the uploads to already exist in the library.

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

Deploy Server

Other Tools