Skip to main content
Glama
thenavidm

Kit MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create a broadcast

create_broadcast
Destructive

Create and schedule email broadcasts to reach subscribers, with options for filtering, publishing, and template selection.

Instructions

Create a broadcast. May affect delivery, audience membership, published data or irreversible state. Requires confirm=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
publicNo`true` to publish this broadcast to the web. The broadcast will appear in a newsletter feed on your Creator Profile and Landing Pages.
accountNoNamed private account from KIT_ACCOUNTS. Defaults to KIT_DEFAULT_ACCOUNT or the first configured account.
confirmNoMust be true for audience/delivery changes, publishing, destructive operations and signing-secret changes. Use only for an action requested by the user.
contentNoThe HTML content of the email. On a `Classic` template this is the body, and the template adds the design around it when the broadcast is sent. On a `Starting point` template the design lives in the body, so this is the complete email: keep the wrappers, images, inline styles and Liquid tags, including `{{ unsubscribe_url }}` and `{{ address }}`. Without an unsubscribe link the broadcast can't be sent. A read returns the string that was written, so `GET`, `PUT`, `GET` round-trips, apart from Kit's own "Built with Kit" badge, which a `Starting point` write takes out of the body and re-applies when the email renders. A broadcast built in Kit's editor reads back as Kit's rendered HTML instead, and writing that back replaces its individually-editable blocks with one HTML block. Sending `content` in the same request as a `Starting point` `email_template_id` also needs `allow_starting_point: true`. Omit `content` and name a `Starting point` template in `email_template_id` to create the broadcast with that template's own design.
payloadNoComplete JSON body instead of individual body flags. Supports nullable fields and nested bulk structures. Cannot be combined with body flags or payload_file.
send_atNoThe scheduled send time for this broadcast in ISO8601 format. If no timezone is provided, UTC is assumed.
subjectNo
descriptionNo
payload_fileNoLocal JSON request body file, at most 5 MB. Contents are validated before the API call and are never logged.
preview_textNo
published_atNoThe published timestamp to display in ISO8601 format. If no timezone is provided, UTC is assumed.
email_addressNoThe sending email address to use. Uses the account's sending email address if not provided.
thumbnail_altNo
thumbnail_urlNo
email_template_idNoId of the email template to use. Uses the account's default template if not provided. 'Starting point' template is not supported.
subscriber_filterNoFilters your subscribers. At this time, we only support using only one filter group type via the API (e.g. `all`, `any`, or `none` but no combinations). If nothing is provided, will default to all of your subscribers.
allow_starting_pointNoExplicitly allow replacing a Starting point template body, as described in Kit’s current content-field documentation. Review the complete rendered HTML first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

B3.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark the tool as destructive, non-idempotent, open-world, and not read-only. The description adds meaningful context beyond those hints by naming affected domains: delivery, audience membership, published data, and irreversible state, plus the confirm requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences with no waste. The purpose is front-loaded, followed by safety impact and the confirmation requirement. It is appropriately sized for an at-a-glance description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive creation tool with a very rich schema and safety annotations, the description covers the minimum: it says what it creates, warns of destructive effects, and states the confirm requirement. However, it omits selection guidance against siblings and does little to help an agent choose this tool rather than another creation or update tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 17 parameters and 71% description coverage. The description mentions only confirm=true, which the schema already documents, and adds no meaning about content, payload, subscriber_filter, templates, or scheduling. It does not compensate for the remaining parameter gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Create a broadcast.' An agent can tell what the tool does. It does not differentiate from siblings such as create_sequence or update_broadcast, and the first sentence largely restates the title, so it is clear but not maximally informative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description notes effects and a confirm prerequisite, but it gives no guidance on when to choose this tool over alternatives, when not to use it, or what conditions select a different create tool. The requirement 'confirm=true' is a constraint rather than usage routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools