Skip to main content
Glama

delete_asset_folder

Delete an asset folder from your Storyblok space by providing its folder ID. Removes the folder and its contents permanently.

Instructions

Delete an asset folder from the current Storyblok space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesID of the folder to delete

Implementation Reference

  • The 'delete_asset_folder' tool handler that takes a folder_id parameter and calls the Storyblok Management API DELETE endpoint /asset_folders/{folder_id}.
    // Tool: delete_asset_folder
    server.tool(
      'delete_asset_folder',
      'Delete an asset folder from the current Storyblok space.',
      {
        folder_id: z.string().describe('ID of the folder to delete'),
      },
      async ({ folder_id }) => {
        try {
          const data = await apiDelete(`/asset_folders/${folder_id}`);
          return createJsonResponse(data);
        } catch (error) {
          if (error instanceof APIError) {
            return createErrorResponse(error);
          }
          throw error;
        }
      }
    );
  • The input schema for delete_asset_folder - expects a single 'folder_id' string parameter describing the ID of the folder to delete.
    {
      folder_id: z.string().describe('ID of the folder to delete'),
    },
  • Registration of the registerAssetsFolders function (which registers delete_asset_folder) in the main tool aggregator.
    registerAssetsFolders(server);
  • The registerAssetsFolders function exported from assets-folder.ts that registers all asset folder tools including delete_asset_folder.
    export function registerAssetsFolders(server: McpServer): void {
  • The apiDelete helper function used by delete_asset_folder to make the DELETE HTTP request to the Storyblok Management API.
    export async function apiDelete<T = unknown>(path: string): Promise<T> {
      const url = buildManagementUrl(path);
      const response = await fetch(url, {
        method: 'DELETE',
        headers: getManagementHeaders(),
      });
      return handleResponse<T>(response, url);
    }
Behavior2/5

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

No annotations provided, so description should disclose traits like destructive behavior, permission requirements, or behavior when folder contains assets; it only states the obvious deletion action.

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?

Single sentence, no redundancy; appropriate length but at the expense of completeness.

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?

Lacks details on return value, error handling, or side effects (e.g., what happens if folder has subfolders/assets). With no output schema, more context is needed for safe invocation.

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?

Input schema covers 100% with one parameter (folder_id) described; the description adds no additional meaning beyond the schema's definition.

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 action 'Delete an asset folder' and specifies the scope 'from the current Storyblok space', distinguishing it from related tools like delete_asset or delete_multiple_assets.

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 versus alternatives like delete_asset or delete_multiple_assets; no mention of prerequisites or conditions such as whether the folder must be empty.

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/hypescale/storyblok-mcp-server'

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