Skip to main content
Glama
Unified Canva Skills MCP Server

Unified Canva Skills MCP Server

by JehadurRE

canva_switch_account

Switch the active Canva account by specifying an account_id, or omit it to rotate to the next ready, non-cooled-down account.

Instructions

Switch the active Canva account to a specific account_id or rotate to the next non-cooled-down account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "canva_switch_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoTarget account ID (omit to rotate to the next ready account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that rotation skips 'non-cooled-down' accounts, hinting at rate-limit/cooldown semantics, but it says nothing about side effects on the previously active account, whether the switch is reversible, required permissions, or what is returned.

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?

A single sentence with zero filler, front-loading the primary action and immediately giving the two-mode branching.

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

Completeness4/5

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

For a one-optional-parameter state-switching tool with no output schema, the essential decision information (target vs rotate, cooldown filter) is present; only the return value and failure behavior are left unstated.

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 coverage is 100% and the single parameter's schema description already states 'omit to rotate to the next ready account', so the description largely restates structured data. The one added nuance is the cooldown constraint on which accounts rotation will pick.

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?

States a specific verb (switch) and resource (active Canva account) and enumerates both operating modes in one sentence, so an agent can distinguish it from canva_connect_account or canva_list_accounts without opening any schema.

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?

The description gives a clear selection rule: pass account_id to target a specific account, omit it to rotate to the next ready account. It does not explicitly exclude or route to sibling tools such as canva_connect_account, which is the only missing piece.

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