@ductape/mcp 0.2.28 → 0.2.29

package/dist/index.js

@@ -780,13 +780,16 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
   databases.migration.rollback [migrations, count?]
   databases.migration.history []
   databases.migration.status [migrations]
-  databases.action.create [{ tag: "product:database:action", name, tableName, operation: "query"|"insert"|"update"|"delete"|"upsert"|"aggregate"|"rawSql", template: { where?, select?, limit?, offset?, orderBy?, records?, query?, params?, ... }, description?, filterTemplate? }]
+  databases.action.create [{ tag: "product:database:action", name, description, tableName, operation: "query"|"insert"|"update"|"delete"|"aggregate"|"count", template, filterTemplate? }]
     ← ADMINISTRATIVE (access key required). FORBIDDEN via ductape_execute (publishable key) —
       use ductape_cli("db actions create --action-file action.json") instead. tag MUST be fully qualified
       "product_tag:database_tag:action_tag" — a 2-part "database:action" shorthand only resolves
       inside a long-lived process that already has that product's builder cached, never in a
       fresh CLI/MCP call. This is pure metadata registration; it never connects to the live
       database, so it does NOT require the database to be reachable at call time.
+      MongoDB query example: { operation: "query", template: { where: { email: "{{email}}" } } }
+      Placeholders are {{name}}, never $Input{name}. For the exact manifest call
+      ductape_schema({ module: "product", method: "databases.action.create" }).
   databases.action.update [{ tag, name?, description?, template?, filterTemplate? }]
     ← ADMINISTRATIVE. Use ductape_cli("db actions update --tag <tag> --action-file patch.json").
   databases.action.fetch  [action_tag]  ← read-only, safe via ductape_execute
@@ -2432,10 +2435,12 @@ shape and do not resolve a saved action.
 Create/update/delete are ADMINISTRATIVE (access key) — FORBIDDEN through ductape_execute
 (publishable key). Use ductape_cli, same as every other admin resource:
   ductape_cli("db actions create --action-file action.json")
-    File: { tag: "product:database:action", name, tableName,
-             operation: "query"|"insert"|"update"|"delete"|"upsert"|"aggregate"|"rawSql",
-             template: { where?, select?, limit?, offset?, orderBy?, records?, query?, params? },
-             description?, filterTemplate? }
+    File: { tag: "product:database:action", name, description, tableName,
+             operation: "query"|"insert"|"update"|"delete"|"aggregate"|"count",
+             template, filterTemplate? }
+    MongoDB query: { operation: "query", template: { where: { email: "{{email}}" } } }
+    Placeholders use {{name}}, never $Input{name}. Call
+    ductape_schema({ module: "product", method: "databases.action.create" }) for the exact shape.
     tag MUST be fully qualified "product_tag:database_tag:action_tag" — the SDK's 2-part
     "database:action" shorthand only works inside one already-warm process, never a fresh CLI call.
     This is pure metadata registration — it does not connect to the live database, so the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ductape/mcp",
-  "version": "0.2.28",
+  "version": "0.2.29",
   "description": "MCP server that exposes Ductape SDK operations via the backend proxy",
   "type": "module",
   "main": "dist/index.js",