Save a 3D viewport screenshot as an image file. Specify absolute path and optional pixel dimensions to generate a thumbnail for previews or documentation.
Export a 3D viewport screenshot/thumbnail.
Args: file_path: Absolute path for the exported image file. width: Image width in pixels (default 512). height: Image height in pixels (default 512).
| Name | Required | Description | Default |
|---|---|---|---|
| width | No | ||
| height | No | ||
| file_path | Yes |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool exports an image with specified width/height, but does not mention side effects, required viewport state, file format, or whether it is read-only. This is minimal but not misleading.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded with the primary purpose, followed by a clearly structured Args list. No unnecessary words, though the Args section is largely restating schema fields with added semantic detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the essential mechanics of the tool, but lacks usage context, output/return behavior, and any discussion of file format or overwrite behavior. Given the tool's simplicity, it is adequate but has clear gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds meaning to all three parameters: file_path is an absolute path for the exported image, width and height are in pixels with defaults. This is more informative than the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: 'Export a 3D viewport screenshot/thumbnail.' This distinguishes it from generic export tools, though it does not explicitly differentiate from closely related siblings like export_snapshot or capture_3d.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives. The description does not mention export_snapshot, capture_3d, or any conditions that would make export_thumbnail the preferred choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.