Skip to main content
Glama
Unified Canva Skills MCP Server

Unified Canva Skills MCP Server

by JehadurRE

canva_get_skill

Load a bundled skill's full SKILL.md or a targeted reference guide to retrieve exact instructions for Canva design workflows.

Instructions

Load the full SKILL.md or a specific reference markdown guide (e.g. 'canva-mcp-tools.md') for a bundled skill.

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": {
      "skill_id": "<skill_id>"
    },
    "name": "canva_get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skill_idYesSkill directory name (e.g. 'canva-studio', 'canva', 'pptx-presentation-designer').
referenceNoOptional reference filename inside the skill's references/ directory.

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 carries the full behavioral burden. 'Load' reasonably implies a read-only retrieval and the text clarifies that 'reference' resolves inside the skill's references/ directory, but it says nothing about the returned form (raw markdown text), size limits, or what happens for an invalid skill_id or missing reference file.

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?

A single front-loaded sentence with the verb and resource up front and no filler. The parenthetical example is useful rather than padding, though the phrasing is slightly dense with nested qualifiers.

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 two-parameter retrieval tool with full schema coverage and no output schema, the description covers the core what-and-which-file question. It stops short of stating the return type or error behavior, which matters because nothing else in the definition documents the response.

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 100%, so the baseline is 3, but the description adds real meaning: it clarifies that omitting 'reference' yields the full SKILL.md, which the schema's 'Optional reference filename' wording does not state. It also supplies a concrete reference example ('canva-mcp-tools.md') reinforcing the expected filename form.

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 uses a specific verb ('Load') and names the exact resources ('the full SKILL.md or a specific reference markdown guide') for a bundled skill, so an agent knows it retrieves skill documentation content. It does not explicitly distinguish itself from the sibling canva_list_skills, leaving the enumeration-vs-retrieval split to inference.

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 only implied: the wording suggests you call this to fetch content after knowing a skill id, but there is no explicit 'use this when...' or 'use canva_list_skills first to discover ids' guidance. No exclusions or prerequisites are stated.

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