Skip to main content
Glama
Unified Canva Skills MCP Server

Unified Canva Skills MCP Server

by JehadurRE

canva_remote_call

Call any remote Canva MCP tool with automatic 401 token refresh and multi-account rotation on quota limits, enabling design creation, editing, and export without manual auth handling.

Instructions

Call any remote Canva MCP tool (create-design, get-create-design-async-job, copy-design, merge-designs, get-design, start-editing-transaction, perform-editing-operations, commit-editing-transaction, upload-asset-from-url, export-design, etc.) with automatic 401 token refresh and zero-wait multi-account rotation on quota_cooldown.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tool_name": "<tool_name>"
    },
    "name": "canva_remote_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsNoTool arguments object.
tool_nameYesRemote Canva MCP tool name.
account_idNoOptional starting account ID.
auto_rotateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description usefully discloses the automatic 401 token refresh and quota_cooldown-driven multi-account rotation, plus that auto_rotate defaults on. It omits the safety profile of a tool that can execute writes (commit-editing-transaction, merge-designs, upload-asset-from-url) and says nothing about what happens on remote-tool errors or invalid tool names.

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?

One front-loaded sentence with no filler; the parenthetical example list is long but each name earns its place by illustrating routable operations. It could be split for readability but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a generic proxy with a nested arguments object and no output schema, the description covers the auth/rotation layer but not the return shape, error surface, or how to discover valid tool_name values. An agent can call it, but not confidently recover from failures.

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?

Schema coverage is 75%, so the baseline would be 3, but the description adds real meaning: the example tool names define the value space for tool_name, and 'multi-account rotation on quota_cooldown' explains what auto_rotate actually governs. The nested arguments object and account_id interplay are only lightly covered.

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?

States a specific action and resource: it dispatches a call to a named remote Canva MCP tool, with the example list making the scope concrete. It stops short of differentiating itself from canva_remote_discover, which an agent would likely need to find valid tool_name values.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The enumerated example tool names implicitly show what kinds of operations to route through this dispatcher, which is meaningful guidance. However, there is no explicit when/when-not statement and no mention of the discover sibling that would supply valid tool_name values, leaving the agent to infer the workflow.

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