Skip to main content
Glama
Berrio

inkscape-mcp

by Berrio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

export_svg

Exports SVG documents as Inkscape SVG or plain SVG through a bounded Inkscape pipeline.

Instructions

Exports an SVG as Inkscape SVG or plain SVG through the bounded Inkscape pipeline.

Input Schema

NameRequiredDescriptionDefault
pathYes
flavorYes
outputPathYes
textToPathNo
workspaceIdYes
selectionIdsNo
expectedRevisionYes
expectedOutputRevisionNo

Output Schema

NameRequiredDescriptionDefault
hashYes
assetsYes
flavorYes
viewBoxYes
revisionYes
warningsYes
byteLengthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / selectionIds
      Added value: +{
+  "items": {
+    "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
+    "type": "string"
+  },
+  "maxItems": 100,
+  "minItems": 1,
+  "type": "array"
+}
    • addedOutput schema / properties / assets
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "path": {
+        "maxLength": 1024,
+        "minLength": 1,
+        "type": "string"
+      },
+      "revision": {
+        "pattern": "^[a-f0-9]{64}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "path",
+      "revision"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / byteLength
      Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • addedOutput schema / properties / hash
      Added value: +{
+  "pattern": "^[a-f0-9]{64}$",
+  "type": "string"
+}
    • addedOutput schema / properties / viewBox
      Added value: +{
+  "maxLength": 256,
+  "minLength": 1,
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "flavor",
-  "revision",
-  "warnings"
-]New value: +[
+  "assets",
+  "byteLength",
+  "flavor",
+  "hash",
+  "revision",
+  "viewBox",
+  "warnings"
+]
  2. First observedv0.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Only destructiveHint=false is annotated, so the description carries the disclosure burden. It hints that export runs through an Inkscape pipeline (implying an Inkscape dependency) but says nothing about how outputPath is written, whether an existing output is overwritten, or how expectedRevision/expectedOutputRevision concurrency checks behave.

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 no filler, opening with the verb. Its brevity, however, is closer to under-specification than to efficient density for an 8-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema means return values need no explanation, but with 8 params at 0% coverage and near-empty annotations, the description leaves the revision semantics and output-write behavior entirely undocumented for a tool that produces a file.

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 0% across 8 parameters. The description only loosely maps 'Inkscape SVG or plain SVG' to the flavor enum; the required optimistic-concurrency fields (expectedRevision, expectedOutputRevision), path/outputPath, workspaceId, selectionIds, and textToPath are entirely unexplained.

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 (exports) and resource (SVG), and distinguishes the two output flavors (Inkscape vs plain SVG). It reads clearly against SVG-adjacent siblings like export_png, export_pdf, and document_export, though 'bounded Inkscape pipeline' is jargon rather than useful differentiation.

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 guidance on when to choose this over document_export, document_export_batch, export_png, or export_pdf, and no prerequisites or exclusions are stated. Usage is only implied by the noun 'SVG'.

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

Deploy Server

Other Tools