Skip to main content
Glama
elisbanpaco

Canva MCP Server

by elisbanpaco

canva_create_folder

Creates a new folder in Canva to organize designs by project or client, with an optional parent folder for nested structure.

Instructions

Crea una nueva carpeta en Canva.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre de la nueva carpeta.
parentFolderIdNoID de la carpeta padre (opcional).
Behavior2/5

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only states that a folder is created, with no mention of side effects, required permissions, error conditions, duplicate handling, or whether the created folder's ID is returned. For a mutating operation, this is a significant transparency gap.

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 a single, efficient sentence with no wasted words. It is front-loaded with the core purpose, though it is perhaps too minimal to earn full marks for structure given the lack of additional useful context.

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?

For a creation tool with no output schema and no annotations, the description is incomplete. It does not explain what the tool returns, how to reference the new folder afterward, or any conditions that might cause failure. An agent would need to infer behavior from the schema alone.

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 both 'name' and 'parentFolderId'. The description adds no additional meaning beyond the schema, but it does not need to compensate because the parameter documentation is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear action ('Crea') and resource ('una nueva carpeta en Canva'), immediately conveying what the tool does. It is distinguishable from siblings like canva_list_folders or canva_create_design, though it does not explicitly differentiate itself from them.

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 is provided about when to use this tool versus alternatives such as canva_list_folders or canva_list_folder_items. The description implies its use for creating a folder, but it gives no context about prerequisites, parent folder requirements, or when another tool would be more appropriate.

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/elisbanpaco/mcp-canva-gemini-cli'

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