Start an update
start_updateStep 1 of publishing an update to the Microsoft Store: makes the update and returns an upload link for its .msix. Pass appId, the package version (four numbers like 1.4.0.0, higher than the live one; ask the person if you can't tell), and the .msix file name and exact size in bytes (ask the person if you don't know them; Windows shows the size in bytes in the file's Properties). Without a shell, as in ChatGPT: reply to the person with upload.page as a clickable markdown link, like "Upload the .msix here: storefast.app upload page", ask them to tell you when the page says Done, then call finish_upload. A file attached to a message never reaches StoreFast, so send the link even when the person attached the .msix. With a shell, as in Codex or Claude Code: run upload.shell (or PUT each part to upload.urlTemplate), then call finish_upload. The link works for an hour. If it expires, or the app already has an update waiting for its package, call start_update with that releaseId for a fresh link. Nothing reaches Partner Center until submit_update. Uploading again into an update replaces what was uploaded to it, so only send the package that update is for.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "start_update"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | The exact file size in bytes. | |
| appId | No | The app id from list_apps. | |
| version | No | Package version, four numbers like 1.4.0.0. | |
| fileName | No | The .msix file name. | |
| releaseId | No | Only for an update still waiting for its package: a fresh upload link for it. |