Skip to main content
Glama
Adobe XD MCP

Adobe XD MCP

by srayan-uxd

xd_export_component

Export a single component master from an .xd file in the same format as artboard exports, with options for page, depth, assets folder, and semantic layer names.

Instructions

Export one component master (see xd_list_components) in the same format as xd_export_artboard.

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": {
      "file": "<file>",
      "component": "<component>"
    },
    "name": "xd_export_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to a .xd file
pageNoPage of a large export (see pageCount / hasMore in the result).
depthNoMax nesting depth (default: everything). Layers below the limit are marked truncated:true; nothing is ever cut silently.
assetsDirNoOptional absolute folder (inside the allowed roots). Referenced images are saved there as <imageRef>.<ext>.
componentYessymbolId or component name
semanticNamesNoAdd suggestedName to every layer (numeric suffixes stripped, text-based names).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • changedInput schema / properties / depth / description
      Previous value: -"Max nesting depth. Auto-reduced if the result is too large."New value: +"Max nesting depth (default: everything). Layers below the limit are marked truncated:true; nothing is ever cut silently."
    • addedInput schema / properties / page
      Added value: +{
      +  "default": 0,
      +  "description": "Page of a large export (see pageCount / hasMore in the result).",
      +  "maximum": 1000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / semanticNames
      Added value: +{
      +  "default": false,
      +  "description": "Add suggestedName to every layer (numeric suffixes stripped, text-based names).",
      +  "type": "boolean"
      +}
  2. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the export uses the same format as xd_export_artboard, but does not explain what that format is, whether the operation is read-only, how assetsDir writes are handled, or how pagination/truncation behave in the result. These details appear only in the schema parameter descriptions, not in the tool description itself.

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?

The description is a single compact sentence with no filler. It front-loads the core action and uses parenthetical and comparative references efficiently. Every phrase contributes to identifying the resource or the output format.

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 six-parameter export tool with no output schema and no annotations, the description is somewhat thin. It points to xd_export_artboard for format compatibility, which is useful, but it does not explain the return shape or key behavioral details like pagination and asset writing. The rich schema descriptions compensate partially, but the description alone leaves gaps.

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%, so all six parameters are already documented in the input schema. The description adds only that a component master is exported in the xd_export_artboard format and does not elaborate on component, page, depth, assetsDir, or semanticNames semantics. The baseline of 3 is appropriate because the schema does the heavy lifting.

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 states a specific verb and resource: export one component master, with a pointer to xd_list_components for discovery. It also clarifies the output format by comparing it to xd_export_artboard, which helps distinguish it from listing tools. It stops short of fully differentiating why one would choose this over xd_export_svg or xd_render_artboard, so it is clear but not maximally precise.

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 mention of xd_list_components gives implied guidance on where to obtain the component identifier, and the name plus description imply this is for exporting components rather than artboards. However, there is no explicit when-to-use versus when-not-to-use guidance, and no alternatives are named for different export formats. Usage is inferable but not explicitly framed.

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