Skip to main content
Glama
webapper-services

CloudSee Drive MCP Server

by webapper-services
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Rename file or folder

rename_file
Destructive

Rename a file or folder in a S3-backed CloudSee Drive using its exact key and storage ID. Requires explicit confirmation to complete the rename asynchronously.

Instructions

Rename a file or folder in a drive, addressed by its exact object key plus its storage id (the StorageId field from search_files / browse_folder / get_file_metadata — not from list_files or recent_files, whose ids are a different id space and will NOT work). Queued: returns a RequestId and the rename completes in the background, typically under 2 minutes — verify by listing until the new name appears. The StorageId goes stale while the rename is in flight, and StorageId is what delete_files and move_file require, so re-read it from a listing once the new name appears rather than reusing the one you renamed with. Requires the drive (bucketName). Destructive (changes the object's key). Requires confirm=true. (Write access is authorized server-side by the public API's RBAC — a denial means the API key lacks this tool's scope, not a tool failure.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to actually perform this mutating/irreversible action. If omitted or false, the tool returns a preview and makes no changes.
newNameYesNew name.
isFolderNoSet true when renaming a folder.
objectKeyYesExact object key of the file or folder as returned by a listing tool (folders keep their trailing slash).
storageIdYesStorage/index id of the object — the StorageId field returned by search_files, browse_folder, or get_file_metadata. NOTE: the ids from list_files and recent_files belong to a different id space and will NOT work here.
bucketNameNoThe CloudSee drive (S3 bucket) name to operate in, e.g. 'max-2778abc0' — find it in the CloudSee dashboard. Required unless CLOUDSEE_DEFAULT_BUCKET is configured on the server.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.1
    • changedInput schema / properties / storageId / description
      Previous value: -"Storage/index id of the object — the StorageId field returned by the INDEXED listing tools (search_files, browse_folder, recent_files). NOTE: list_files reads straight from storage and returns a different id that will NOT work here."New value: +"Storage/index id of the object — the StorageId field returned by search_files, browse_folder, or get_file_metadata. NOTE: the ids from list_files and recent_files belong to a different id space and will NOT work here."
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Even though annotations already mark the tool as destructive and non-read-only, the description adds substantial behavioral context: it returns a RequestId and completes asynchronously, the StorageId becomes stale during the rename, and a permission denial means the API key lacks scope rather than a tool failure. This aligns with the annotations and adds real behavioral value.

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 description is dense but not bloated; every major point (id source, async behavior, stale id, bucketName, confirm, RBAC) earns its place. It is longer than strictly necessary, but the added caveats are operationally important for safe invocation.

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?

For a destructive asynchronous tool with no output schema, the description covers invocation prerequisites, completion timing, verification steps, and error interpretation. No critical operational information needed to call the tool correctly 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 coverage is 100%, and the schema already documents storageId id-space caveats and confirm. The description reinforces these and adds operational meaning beyond the schema by warning that StorageId goes stale in flight and that delete_files/move_file depend on re-reading a fresh StorageId.

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 states a precise verb and resource ('Rename a file or folder in a drive') and distinguishes the required addressing mode: exact object key plus storage id. It also names the exact source tools that produce a compatible storage id, making it clear what this tool operates on.

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

Usage Guidelines4/5

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

The description conveys clear operating context: queued background execution, verify by listing until the new name appears, and the requirement for bucketName and confirm=true. It does not explicitly contrast with move_file as an alternative, so it stops short of full when-to-use versus when-not-to-use guidance.

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