Gear

Overview Schema Source Related Servers Discussions Admin

export-presets

Lists all export presets from export_presets.cfg to show available targets such as Windows, Linux, and Android. Use this before exporting a project.

Instructions

[compact alias of list_export_presets] Lists all export presets defined in export_presets.cfg. Use before export_project to see available targets (Windows, Linux, Android, etc.).

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": {
      "projectPath": "<projectPath>"
    },
    "name": "export-presets"
  }
}

Input Schema

Name	Required	Description	Default
`projectPath`	Yes	Absolute path to project directory containing project.godot. Use the same path across all tool calls in a workflow.
`includeTemplateStatus`	No	If true (default), shows if export templates are installed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1May 7, 2026

TDQS

A4/5.0

Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits beyond listing presets, such as read-only nature, side effects, or permissions. The description only states the basic operation.

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?

The description is very concise (two sentences) and front-loaded with the purpose. It is efficient but could be slightly expanded for completeness without losing brevity.

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

Completeness5/5

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

Given the tool's simplicity, full schema coverage, and the description's context about when to use it (before export) and example targets, the description is fully adequate.

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 coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema, which already describes both parameters (projectPath and includeTemplateStatus).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists all export presets from export_presets.cfg, and identifies itself as an alias of list_export_presets, providing a specific verb and resource.

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

Usage Guidelines5/5

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

It explicitly advises to use before export_project to view available targets (e.g., Windows, Linux, Android), giving clear when-to-use context and distinguishing it from sibling tools like export-run.

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