Skip to main content
Glama
Sign In

Editmamei Connect

by io.github.editmamei
OverviewDiscussionsAdmin

share_edit

Prepare a page that shows the user how this edit was made, so they can share it: before and after, a picture for each step that changed the look, and a plain list of the steps. Call it for an image you edited in this conversation, once the user is happy with the result and wants to share it, by the id you edited it under: do not reopen the photo to share it, because a reopened photo starts a new history and the page would show none of the edit. It makes a DRAFT only and returns a confirm link; give that link to the user, who confirms there before anything is public. It also looks for license plates and faces in the before and the after picture and reports what it finds in each: if it finds any, offer to blur or remove them first (a masked blur stays on in every picture), then call it again. It takes about a minute. Your adjustments are left exactly as they were. Give it chapters: the edit told as a few chunks of work, each saying in plain words what it did to the photo (for example "Brought out the water: selected the water and lifted its turquoise and depth"), not tool names. To write them, first call it with preview: true: it returns the numbered steps at once, with no draft and no pictures; then call it once with your chapters. Chapters that do not fit are refused before anything is made. To change a draft's title or chapters afterwards, call it with that draft's share_id and title or chapters: it revises the draft, with no new pictures. Sharing the same photo again (after more edits) makes a new draft that replaces its earlier unconfirmed one.

Input Schema

NameRequiredDescriptionDefault
imageNoThe id of the edited image, as returned by open_photo. Required unless `share_id` is given.
titleNoA short title for the page (at most 80 characters). Default: "My edit".
previewNoTrue returns the numbered steps (and the chapters, checked, when given) at once, with no draft and no pictures. Default false.
chaptersNoAt most 8 chapters covering every step once, in order. Without them the steps are grouped by kind of work.
share_idNoA draft's share_id, from an earlier call: revises that draft's `title` or `chapters` instead of making a new one, with no new pictures.
include_beforeNoWhether the page shows the before picture and a picture for each step (default true). False shares the after picture and the list of steps alone, for an edit whose original must not be shown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / image / description
      Previous value: -"The id of the edited image, as returned by open_photo."New value: +"The id of the edited image, as returned by open_photo. Required unless `share_id` is given."
    • addedInput schema / properties / preview
      Added value: +{
+  "description": "True returns the numbered steps (and the chapters, checked, when given) at once, with no draft and no pictures. Default false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / share_id
      Added value: +{
+  "description": "A draft's share_id, from an earlier call: revises that draft's `title` or `chapters` instead of making a new one, with no new pictures.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "image"
-]
  2. Changed1 schema field changed
    • addedInput schema / properties / chapters
      Added value: +{
+  "description": "At most 8 chapters covering every step once, in order. Without them the steps are grouped by kind of work.",
+  "items": {
+    "properties": {
+      "steps": {
+        "description": "The first and last step it covers, numbered from 1.",
+        "items": {
+          "minimum": 1,
+          "type": "integer"
+        },
+        "maxItems": 2,
+        "minItems": 2,
+        "type": "array"
+      },
+      "text": {
+        "description": "One or two plain sentences on what changed in the photo and why.",
+        "maxLength": 200,
+        "type": "string"
+      },
+      "title": {
+        "description": "What this chunk of work did, e.g. \"Brought out the water\".",
+        "maxLength": 60,
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "steps"
+    ],
+    "type": "object"
+  },
+  "maxItems": 8,
+  "type": "array"
+}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly=false, destructive=false, openWorld=true, idempotent=false; the description goes far beyond that by disclosing that it makes a DRAFT only, returns a confirm link the user must act on, scans for faces and license plates with a blur/remove follow-up flow, takes about a minute, leaves adjustments untouched, and that re-sharing replaces the prior unconfirmed draft.

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?

It is front-loaded with the purpose and then usage, and nearly every sentence carries operational information. The block is long and a few clauses overlap with schema text (e.g. chapter limits), but the density is justified by the tool's multi-mode behavior.

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?

With no output schema, the description supplies the missing return contract (confirm link, or numbered steps in preview mode) and covers side effects, timing, safety scanning, and the revision/replacement rules. An agent has everything needed to call it correctly in each mode.

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?

Schema coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema for two params: it explains how to author chapters (plain words about the photo, not tool names, with a worked example) and how preview and share_id interact with the main call.

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 opening sentence states a precise verb and artifact: prepare a shareable page showing before/after, a picture per step, and a plain step list. It is immediately distinguishable from siblings like export_photo or make_carousel, which produce different outputs.

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 gives explicit trigger conditions (an image edited in this conversation, user happy and wants to share), the correct identifier to use, and a named anti-pattern (do not reopen the photo, because a reopened photo starts a new history). It also spells out the preview-then-commit flow and the share_id revision path.

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

All Editmamei Connect toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources