Skip to main content
Glama

Canva

by com.canva.mcp
OverviewDiscussionsAdmin

Resize Design

resize-design

Adapt a Canva design to a different canvas size, keeping its content while rearranging and resizing its layout.

Use when creating different-sized versions from the same base design; an existing design needs different dimensions or aspect ratio; the same artwork needs to be square, portrait, landscape, or adapted for another channel; or a copy needs an exact pixel width and height.

Not for resizing a single element.

Each call creates a new resized design and leaves the original unchanged. Returns the new design's design_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
design_idYesID of the existing Canva design to resize. Design IDs start with "D".
design_typeYesTarget design type (preset or custom). Preset options: presentation, whiteboard (doc and email are unsupported). Custom options: width and height in pixels.
user_intentNoMandatory description of what the user is trying to accomplish with this tool call. This should always be provided by LLM clients. Please keep it concise (255 characters or less recommended).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / design_id / description
      Previous value: -"ID of the design to resize. Design ID starts with \"D\"."New value: +"ID of the existing Canva design to resize. Design IDs start with \"D\"."
    • changedInput schema / properties / design_type / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "description": "Use this when resizing to a preset design type. Provide 'type: preset' and 'name'.",
-    "properties": {
-      "name": {
-        "description": "The preset design type name. Options: 'presentation', 'whiteboard'.",
-        "enum": [
-          "presentation",
-          "whiteboard"
-        ],
-        "type": "string"
-      },
-      "type": {
-        "const": "preset",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "name"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "description": "Use this when resizing to custom dimensions. Provide 'type: custom', 'width', and 'height'.",
-    "properties": {
-      "height": {
-        "description": "Height of the design in pixels. Must be at least 1.",
-        "minimum": 1,
-        "type": "number"
-      },
-      "type": {
-        "const": "custom",
-        "type": "string"
-      },
-      "width": {
-        "description": "Width of the design in pixels. Must be at least 1.",
-        "minimum": 1,
-        "type": "number"
-      }
-    },
-    "required": [
-      "type",
-      "width",
-      "height"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "description": "Use this when resizing to a preset design type. Provide 'type: preset' and 'name'.",
+    "properties": {
+      "name": {
+        "description": "Preset canvas size for the new design. Use \"presentation\" for slides or \"whiteboard\" for a whiteboard.",
+        "enum": [
+          "presentation",
+          "whiteboard"
+        ],
+        "type": "string"
+      },
+      "type": {
+        "const": "preset",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "name"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Use this when resizing to custom dimensions. Provide 'type: custom', 'width', and 'height'.",
+    "properties": {
+      "height": {
+        "description": "Height of the new design in pixels.",
+        "minimum": 1,
+        "type": "number"
+      },
+      "type": {
+        "const": "custom",
+        "type": "string"
+      },
+      "width": {
+        "description": "Width of the new design in pixels.",
+        "minimum": 1,
+        "type": "number"
+      }
+    },
+    "required": [
+      "type",
+      "width",
+      "height"
+    ],
+    "type": "object"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses a key side-effect guarantee: each call creates a new resized design and leaves the original unchanged. It also states the return value ('Returns the new design's design_id'), which is especially useful because no output schema is provided.

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 compact and front-loaded: core behavior first, followed by usage conditions, an exclusion, and the return value. Every sentence earns its place without repeated information.

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 3-parameter tool with a fully documented schema, the description covers the input context, the exclusion case, the non-destructive behavior, and the return value. The missing output schema is mitigated by explicitly stating that the new design_id is returned.

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%, and the schema already documents design_id, design_type, preset/custom options, width, height, and user_intent. The description adds little beyond the schema, so the baseline of 3 is appropriate.

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 names a specific operation: 'Adapt a Canva design to a different canvas size' while keeping its content and rearranging/resizing the layout. It differentiates itself from copy-only or edit-only tools and explicitly excludes element-level resizing, so an agent can identify what the tool does.

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?

It provides a clear 'Use when' list with concrete triggering conditions, including different dimensions, aspect ratios, channel adaptation, and exact pixel sizes. It also states a clear exclusion ('Not for resizing a single element'), though it does not name a specific alternative sibling tool.

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

All Canva 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