get_edit_historyRetrieve the full edit history of a generated image, including the original version and every applied edit, to identify the current version before reverting changes.
Get the edit history of a generated image — original version plus every applied edit, with which version is current. Use before reverting an edit.
| Name | Required | Description | Default |
|---|---|---|---|
| output_id | No | ||
| output_index | No | ||
| generation_id | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by explaining what the result contains: original version, applied edits, and current version.
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?
Two tight sentences with no wasted wording. The core purpose and the key usage rule are front-loaded.
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 adequately explains the conceptual return value despite there being no output schema. However, for a tool with three undocumented parameters, it leaves the agent without enough information to choose or supply identifiers correctly.
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?
The schema has 3 parameters with 0% description coverage and no required fields, yet the description does not explain what output_id, output_index, or generation_id mean or how they should be used. It therefore fails to compensate for the missing schema semantics.
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?
States a specific verb and resource: get the edit history of a generated image. It also clarifies the return scope — original version plus every applied edit and the current version — and distinguishes it from the sibling revert_edit by tying its use to reverting.
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?
Provides a clear usage condition: 'Use before reverting an edit.' This explicitly links the tool to the sibling revert_edit, but it does not spell out when not to use this tool or name other alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.