Skip to main content
Glama

Image Export

image_export
Read-only

Saves an image component's uploaded file to a local path (a folder preserves the original name) without changing the report, enabling image copies between reports.

Instructions

Save an image component's uploaded file to a local path (a folder keeps the original file name). Read-only for the report; use it to copy images between reports (then image_upload_set).

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": {
      "page_id": "<page_id>",
      "component_id": "<component_id>",
      "path": "<path>"
    },
    "name": "image_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
page_idYes
report_idNo
component_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.9/5.0
Behavior3/5

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

The readOnlyHint=true annotation is consistent with the description's claim that the operation is read-only for the report, and the description usefully clarifies that a filesystem write does occur. Beyond that it does not say whether existing files are overwritten, what happens on a missing directory, or what errors look like, so it adds only modest context on top of the annotation.

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?

Two compact sentences with the core action front-loaded and the destination nuance immediately attached. No filler or restated title.

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?

An output schema exists, so return values need not be covered, and the report-safety profile is handled by annotations. However, for a four-parameter tool with zero schema documentation, the description leaves three parameters and the failure/overwrite semantics unaddressed.

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 0% across four parameters, so the schema itself explains nothing. The description compensates only for `path` (local destination, folder retains original filename); page_id, component_id, and especially the optional/nullable report_id are left unexplained.

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?

States a specific verb and resource — saving an image component's uploaded file to a local path — and clarifies folder behavior. The parenthetical reference to image_upload_set distinguishes it from the sibling transfer tool.

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

Usage Guidelines4/5

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

Gives an explicit use case (copying images between reports) and names the follow-on tool image_upload_set. It stops short of stating when not to use it or what happens if the target path already exists.

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