@productmaker/mcp 2.10.1 → 3.0.2

package/README.md

@@ -118,8 +118,6 @@ separate release step.
 | `list_meta_destinations`     | List Meta Business portfolios, ad accounts per portfolio, and Facebook Pages; use the returned IDs to choose the exact publication destination                                                                                                                  |
 | `request_media_upload`       | Open the consumer-neutral inline file picker for ProductMaker tasks, image/video creatives, landings, and Meta; supports image, video, or mixed sessions, ChatGPT file references, an explicit OK chat handoff, and `/upload-media` only as fallback            |
 | `check_media_upload`         | Return verified owner-scoped opaque asset IDs and media kinds from a universal upload session; no bytes, token, file name, or private URL reaches the model                                                                                                     |
-| `request_meta_media_upload`  | Backward-compatible Meta upload alias; existing clients keep the legacy staged-source flow                                                                                                                                                                      |
-| `check_meta_media_upload`    | Backward-compatible Meta status alias returning legacy staged asset IDs                                                                                                                                                                                         |
 | `list_tiktok_advertisers`    | List connected TikTok Ads advertiser accounts                                                                                                                                                                                                                   |
 | `publish_to_shopify`         | Publish a completed task to a Shopify store (returns markdown with landing + product URLs)                                                                                                                                                                      |
 | `publish_to_meta`            | Create a Meta Ads campaign from a task (always PAUSED) after selecting exact `portfolioId`, `adAccountId`, and `pageId` with `list_meta_destinations`                                                                                                           |
@@ -155,19 +153,13 @@ presses OK, continue the previous request with only the verified `assetId` and
 matching `mediaKind` values. `check_media_upload` remains available for hosts
 that need an explicit status call.
 
-Existing Meta clients may continue using `request_meta_media_upload` and
-`check_meta_media_upload`. For every legacy entry in `assets[]`, use its
-`mediaKind` as the creative `type` and its `stagingAssetId` as:
-
-```json
-{ "type": "staged", "stagingAssetId": "..." }
-```
-
-inside `publish_creatives_to_meta`. A partial batch may include only the assets
-that `assets[]` actually reports as uploaded. The browser uploads directly to
-the presigned CDN object; the chat never receives file bytes, base64, or a
-local path, and ProductMaker deletes the staging object after a successful
-paused Meta publication (or via the 24-hour TTL cleanup if the flow is
+For Meta, pass each verified asset as
+`{ "type": "asset", "assetId": "..." }` to `publish_creatives_to_meta` after
+the user chooses the portfolio, ad account, and page in chat. A partial batch
+may include only the assets actually reported as uploaded. The browser uploads
+directly to the presigned CDN object; the chat never receives file bytes,
+base64, or a local path, and ProductMaker deletes the staging object after a
+successful paused Meta publication (or via the 24-hour TTL cleanup if the flow is
 abandoned).
 
 ## Video duration and winner review