Skip to main content
Glama
Unified Canva Skills MCP Server

Unified Canva Skills MCP Server

by JehadurRE

canva_list_skills

Lists all bundled Canva and design skills, including their reference guides and helper scripts, so you can discover available capabilities.

Instructions

List all bundled Canva and design skills along with their reference guides and helper scripts.

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

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 behavioral burden; it implies a static, side-effect-free enumeration but never states that it is read-only or non-mutating. It also says nothing about ordering, pagination, or whether the catalog is fixed versus account-dependent, though the zero-parameter signature keeps the risk profile low.

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 the action first and the payload detail second; no filler, no restatement of the title, and nothing that could be trimmed without losing information.

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-parameter, read-only listing tool with no annotations and no output schema, the description covers what is enumerated, which is the main thing an agent needs. It leaves the return shape (e.g., list vs. grouped structure, skill identifiers vs. names) unspecified, which matters since there is no output schema to consult.

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 there is no parameter meaning to add and the baseline is 4. The description correctly does not invent filtering or scoping options that the schema does not offer.

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 gives a specific verb ('List') and a specific resource ('bundled Canva and design skills'), plus what each entry carries (reference guides and helper scripts). It does not differentiate from the obvious sibling canva_get_skill, which presumably returns a single skill's detail, so the agent must infer that boundary.

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?

Use is only implied: 'List all' signals a discovery/browse step that would naturally precede canva_get_skill. There is no explicit when-to-use, no statement that callers should follow up with canva_get_skill for a single skill, and no exclusion of any alternative.

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