Regenerate Template Draft
senderkit_templates_regenerateRegenerate an existing DRAFT template from a new brief. This replaces the draft's content and discards any manual edits made in the editor. Only drafts can be regenerated; published templates are left untouched.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"slug": "<slug>",
"brief": "<brief>",
"context": "<context>"
},
"name": "senderkit_templates_regenerate"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Slug of the DRAFT template to regenerate. | |
| brief | Yes | New brief that fully replaces the draft's content. | |
| context | Yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization." |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Slug of the draft template. | |
| status | Yes | Always draft — this tool never publishes or sends anything. | |
| message | Yes | Human-readable next step to relay to the user. | |
| editorUrl | Yes | Deep link to review and publish the draft in the SenderKit editor. |