Skip to main content
Glama
Unified Canva Skills MCP Server

Unified Canva Skills MCP Server

by JehadurRE

canva_extract_pdf_fonts

Extract embedded TTF/OTF font binaries from Canva-exported PDFs into a target directory for print or Illustrator prepress.

Instructions

Extract all embedded TTF/OTF font binaries from a Canva-exported PDF into a target fonts directory for print or Illustrator prepress.

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": {
      "pdf_path": "<pdf_path>",
      "output_dir": "<output_dir>"
    },
    "name": "canva_extract_pdf_fonts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdf_pathYesPath to exported PDF file.
output_dirYesDirectory where extracted fonts should be saved.

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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key side effect — font binaries are written into an output directory — but says nothing about overwriting existing files, behavior when the PDF contains no embedded fonts, or required filesystem permissions.

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: verb, resource, source, destination, and use case in that order. Nothing is redundant and no sentence needs trimming.

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?

The tool is simple (2 required params, flat schema), and the description covers the core action and output location. With no output schema and no annotations, it could still say what is returned (e.g., count or list of extracted fonts) and how existing files in output_dir are handled.

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 description coverage is 100% and both parameters are documented in the schema itself. The description adds only a slight framing (source is an 'exported' PDF, destination is a 'fonts' directory) beyond what the schema already conveys, so the baseline 3 applies.

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 verb (extract) plus the exact resource (embedded TTF/OTF font binaries) and both the source (Canva-exported PDF) and destination (target fonts directory). It is clearly distinguishable from siblings like canva_inspect_pdf or canva_get_layout_spec, though it never names or contrasts them 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?

The phrase 'for print or Illustrator prepress' gives an implied usage context, which is more than nothing. However, there is no explicit when-to-use/when-not-to-use guidance and no named alternative tool for adjacent needs such as inspecting the PDF first.

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