Skip to main content
Glama
Sign In

ShortSync

by app.shortsync
OverviewDiscussionsAdmin

Create folder

create_folder

Creates a new folder inside a workspace, optionally nested under a parent folder. Folder names must be unique among siblings (case-sensitive, max 80 chars) and nesting is capped at 5 levels. Returns the created folder row. Use list_folders first to look up the parent_id when creating a subfolder.

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name (max 80 chars). Must be unique among siblings under the same parent.
parent_idNoOptional parent folder id. Omit or pass null to create a top-level folder. Must belong to the same workspace.
workspace_idYesWorkspace to create the folder in. Get it from list_workspaces. The user must be a member.
idempotency_keyNoOptional client-generated key (e.g., a UUID) to make retries safe. Identical calls with the same key within 10 minutes return the original result instead of running the write twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses crucial operational behaviors beyond the annotations, specifically: folder name uniqueness (case-sensitive among siblings) and the maximum nesting depth of 5. This is critical execution 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 highly dense and efficient. Every clause adds essential constraints or workflow logic, making it appropriately sized and highly effective.

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?

Given the thorough input schema and the detailed explanation of constraints (nestability, uniqueness, limits), the definition provides all necessary context for the agent to execute the tool correctly.

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?

While schema coverage is 100%, the description adds high-value semantic context by detailing the strict naming constraints (case-sensitive, max 80 chars) and the required prerequisite for nested folders.

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 purpose is perfectly clear: 'Creates a new folder inside a workspace.' It explicitly handles the nuance of optional nesting.

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 provides explicit instructions on workflow, stating 'Use list_folders first to look up the parent_id when creating a subfolder.' It also defines hard operational constraints (80 char limit, 5 level cap).

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

All ShortSync toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources