Skip to main content
Glama
Unified Canva Skills MCP Server

Unified Canva Skills MCP Server

by JehadurRE

canva_list_accounts

Lists connected Canva OAuth accounts and shows the active account, token readiness, and cooldown status so you can verify which account is available before creating or exporting designs.

Instructions

List connected Canva MCP OAuth accounts, active account, token readiness, and cooldown status.

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_list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. "List" implies a non-mutating read and the mention of token readiness and cooldown adds real behavioral context about what state is surfaced, but nothing is said about whether this performs network I/O, requires prior authentication, or how stale the cooldown data may be.

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 front-loaded sentence with no filler; the resource comes first and the reported states follow, so the agent gets the gist immediately.

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 zero-argument read with no output schema, listing the reported fields (accounts, active account, token readiness, cooldown) is exactly the compensation needed. Only the absence of any note about auth preconditions or the shape of the account list keeps it from a 5.

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?

The tool takes zero parameters, so the schema has nothing for the description to expand on; the 4 baseline applies. The description correctly does not invent arguments and instead spends its words on the return surface.

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?

Uses a specific verb ("List") against a specific resource ("connected Canva MCP OAuth accounts") and enumerates what is reported: active account, token readiness, cooldown status. That is enough to distinguish it from canva_connect_account or canva_switch_account, though it never names those siblings explicitly.

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?

Usage is implied rather than stated: because it reports active account, token readiness and cooldown, an agent can infer it is the pre-flight/status check before invoking a remote call. There is no explicit "use this when..." clause and no pointer to the connect or switch alternatives for remediation.

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