update_launch_step

posts:write

Mark a step of a launch kit's plan done (or not done), e.g. once the user has submitted to Product Hunt or finished a prep task. stepId comes from get_launch_kit.

It spends no credits and posts nothing.

Input

• kitIdstring (uuid)required
• stepIdstringrequired

  min length 1 · max length 40

• donebooleanrequired

Permission

Needs the posts:write scope: create drafts. It changes your workspace, so clients may ask you to confirm each call.

Example call

Your assistant sends this for you. It is shown so you can see the shape of a call, with placeholder values for the required fields.

tools/call

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_launch_step",
    "arguments": {
      "kitId": "3f8e2c1a-0000-4000-8000-000000000000",
      "stepId": "string",
      "done": true
    }
  }
}

Same action over the REST API

The tool runs PATCH /v1/orgs/{orgId}/launch-kits/{kitId} as the signed-in user, with the same validation, approval rules and limits. See it in the Launch kits API reference.