Skip to main content
Glama
FullBars

gpt-image-2-mcp

by FullBars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Edit Sessions

list_edit_sessions
Read-onlyIdempotent

Retrieve active iterative-edit sessions to recover a session_id after client reconnect and check which background jobs are still running.

Instructions

List active iterative-edit sessions (in-memory only, discarded on server restart). Useful to recover a session_id after a client reconnect; each entry also reports whether a turn is still running in the background and which job to poll for it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.5.5
    • addedOutput schema / properties / sessions / items / properties / background
      Added value: +{
+  "description": "Requested background; continue turns inherit it when omitted.",
+  "type": "string"
+}
    • addedOutput schema / properties / sessions / items / properties / model
      Added value: +{
+  "description": "Model the session uses; continue turns inherit it.",
+  "type": "string"
+}
    • addedOutput schema / properties / sessions / items / properties / output_format
      Added value: +{
+  "description": "Output format; continue turns inherit it when omitted.",
+  "type": "string"
+}
    • addedOutput schema / properties / sessions / items / properties / pending_job_id
      Added value: +{
+  "description": "Job to poll with get_image_job while state is \"running\".",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / sessions / items / properties / quality
      Added value: +{
+  "description": "Requested quality; continue turns inherit it when omitted.",
+  "type": "string"
+}
    • addedOutput schema / properties / sessions / items / properties / size
      Added value: +{
+  "description": "Requested size; continue turns inherit it when omitted.",
+  "type": "string"
+}
    • addedOutput schema / properties / sessions / items / properties / state
      Added value: +{
+  "description": "\"running\" while a turn is in flight in the background; continue_edit_session refuses until it lands.",
+  "enum": [
+    "idle",
+    "running"
+  ],
+  "type": "string"
+}
    • changedOutput schema / properties / sessions / items / required
      Previous value: -[
-  "session_id",
-  "created_at",
-  "updated_at",
-  "turns",
-  "last_prompt",
-  "last_image_path"
-]New value: +[
+  "session_id",
+  "created_at",
+  "updated_at",
+  "turns",
+  "last_prompt",
+  "last_image_path",
+  "model",
+  "size",
+  "quality",
+  "background",
+  "output_format",
+  "state",
+  "pending_job_id"
+]
  2. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only and non-destructive, and the description adds important behavioral context: sessions are in-memory only, lost on restart, and entries indicate whether a turn is running and which job to poll. This goes beyond the structured hints.

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 sentences, front-loaded with the core action, and no filler. Every clause adds useful information about scope, lifecycle, or return contents.

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?

For a zero-parameter read-only list tool with an output schema already present, the description fully covers purpose, transient behavior, and the practical recovery scenario. Nothing necessary for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema coverage is 100%, so there is nothing for the description to add about parameters. The baseline for no-parameter tools applies.

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 opens with a specific verb and resource: 'List active iterative-edit sessions'. It clearly distinguishes this tool from image-related siblings by focusing on edit sessions and noting they are in-memory only.

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?

The description states a clear use case: recovering a session_id after a client reconnect. It does not explicitly contrast with alternatives like start_edit_session or list_image_jobs, but the context is sufficient for an agent to know when this listing tool is appropriate.

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