Skip to main content
Glama
speakai

Speak AI MCP Server

Official
by speakai

Clone Folder

clone_folder

Duplicate an existing folder and all its contents, with options to rename, reassign users, and preserve the default view.

Instructions

Duplicate an existing folder and all of its contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for the cloned folder
assignToNoUser IDs to assign the cloned folder to
folderIdYesID of the folder to clone
descriptionNoDescription for the cloned folder
isSaveDefaultViewNoWhether to copy the source folder's default view

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoResponse payload from the Speak AI API
Behavior3/5

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false). The description states it duplicates contents, which implies non-destructive copying, but lacks details on side effects like permissions, async behavior, or size limits.

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?

Single sentence, front-loaded with purpose, no filler. Efficient and clear.

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?

Given 5 parameters and a clone operation, the description is too brief. It omits context about return value (though output schema exists), potential delays, or preconditions. Incomplete for a complex tool.

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 all parameters. The description does not add additional meaning beyond the schema, keeping it at baseline.

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 clearly states the tool clones a folder and all its contents, using the verb 'duplicate' and specific resource 'folder'. It distinguishes from siblings like 'clone_folder_view' 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 Guidelines2/5

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

No guidance on when to use this tool vs alternatives. For example, it does not mention that 'clone_folder_view' should be used for cloning only the view, nor any prerequisites or restrictions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/speakai/speakai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server