Skip to main content
Glama
Unified Canva Skills MCP Server

Unified Canva Skills MCP Server

by JehadurRE

canva_inspect_pdf

Inspect Canva-exported PDFs to verify page dimensions, safe margins, embedded fonts, small text spans, and exact bounding boxes before print or export.

Instructions

Inspect a Canva-exported PDF using PyMuPDF: verify page dimensions, safe margin compliance, embedded fonts, <11pt spans, and exact bbox coordinates.

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>"
    },
    "name": "canva_inspect_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdf_pathYesPath to exported PDF file.
max_pagesNo
safe_margin_ptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It implies a non-destructive read ('Inspect', 'verify') and discloses the implementation (PyMuPDF) and the dimensions examined, which is genuinely useful. However it says nothing about failure modes, whether non-Canva PDFs are rejected, whether max_pages truncates the analysis, or what the returned report looks like.

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 a colon and a tight list of checks; every clause carries information and there is no filler or hedging.

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?

Given three parameters, no annotations, and no output schema, the description covers the input intent reasonably well by naming all the checks the tool performs. The notable remaining gap is the shape of the result itself – an 'inspect' tool exists to produce a verdict, and nothing indicates whether the output is a pass/fail summary, a per-page report, or raw coordinate data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% – just pdf_path is documented in the schema. The description gestures at safe_margin_pt via 'safe margin compliance' and 'bbox coordinates', but never explains max_pages (its default of 5, and whether it caps pages analysed or pages returned) or the unit/threshold semantics of safe_margin_pt. It only partially compensates for the coverage gap.

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 names a specific verb (Inspect) and a specific resource (Canva-exported PDF) and then enumerates five concrete checks: page dimensions, safe-margin compliance, embedded fonts, sub-11pt spans, and bbox coordinates. This clearly separates it from a narrow sibling like canva_extract_pdf_fonts, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is referenced. The implied scenario (pre-flight verification of a Canva export before publishing) is inferable from the listed checks, but the agent gets no statement about prerequisites or when a different tool is the better call.

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