Beehiiv MCP Server

Overview Schema Source Related Servers Discussions Admin

Create a tier

create_tier

Destructive

Create a subscription tier for a Beehiiv publication by defining its name, description, and price options; confirm=true is required, and OAuth needs tiers:write.

Instructions

Create a tier. Changes account state and requires confirm=true for the user-requested action. OAuth integrations require tiers:write.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`account`	No	Named private account from BEEHIIV_ACCOUNTS. Defaults to BEEHIIV_DEFAULT_ACCOUNT or the first configured account.
`confirm`	No	Set true only when the user asked for exactly this action.
`payload`	No	Complete JSON body instead of individual body flags. Supports nullable fields and nested bulk structures. Cannot be combined with body flags or payload_file.
`description`	No
`payload_file`	No	Local JSON request body file, at most 5 MB. Contents are validated before the API call and are never logged.
`publication_id`	Yes	The prefixed ID of the publication object
`prices_attributes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv3.0.1Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "prices_attributes": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "amount_cents": {
+          "type": "integer"
+        },
+        "cta": {
+          "type": "string"
+        },
+        "currency": {
+          "enum": [
+            "usd",
+            "aud",
+            "cad",
+            "eur",
+            "gbp",
+            "inr",
+            "brl",
+            "mxn",
+            "nzd",
+            "dkk"
+          ],
+          "title": "TierPriceCurrency",
+          "type": "string"
+        },
+        "enabled": {
+          "default": true,
+          "type": "boolean"
+        },
+        "features": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "interval": {
+          "enum": [
+            "month",
+            "quarter",
+            "year",
+            "one_time",
+            "donation"
+          ],
+          "title": "TierPriceInterval",
+          "type": "string"
+        },
+        "interval_display": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "currency",
+        "amount_cents",
+        "interval"
+      ],
+      "title": "TierPricesAttributesItem",
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

changedInput schema / properties / confirm / description

Previous value: -"Must be true for every account mutation. Confirms only the user-requested action."New value: +"Set true only when the user asked for exactly this action."

addedInput schema / properties / payload / properties / prices_attributes / $ref
```
Added value: +"#/$defs/prices_attributes"
```

removedInput schema / properties / payload / properties / prices_attributes / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "amount_cents": {
-      "type": "integer"
-    },
-    "cta": {
-      "type": "string"
-    },
-    "currency": {
-      "enum": [
-        "usd",
-        "aud",
-        "cad",
-        "eur",
-        "gbp",
-        "inr",
-        "brl",
-        "mxn",
-        "nzd",
-        "dkk"
-      ],
-      "title": "TierPriceCurrency",
-      "type": "string"
-    },
-    "enabled": {
-      "default": true,
-      "type": "boolean"
-    },
-    "features": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "interval": {
-      "enum": [
-        "month",
-        "quarter",
-        "year",
-        "one_time",
-        "donation"
-      ],
-      "title": "TierPriceInterval",
-      "type": "string"
-    },
-    "interval_display": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "currency",
-    "amount_cents",
-    "interval"
-  ],
-  "title": "TierPricesAttributesItem",
-  "type": "object"
-}

removedInput schema / properties / payload / properties / prices_attributes / type
```
Removed value: -"array"
```
addedInput schema / properties / prices_attributes / $ref
```
Added value: +"#/$defs/prices_attributes"
```

removedInput schema / properties / prices_attributes / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "amount_cents": {
-      "type": "integer"
-    },
-    "cta": {
-      "type": "string"
-    },
-    "currency": {
-      "enum": [
-        "usd",
-        "aud",
-        "cad",
-        "eur",
-        "gbp",
-        "inr",
-        "brl",
-        "mxn",
-        "nzd",
-        "dkk"
-      ],
-      "title": "TierPriceCurrency",
-      "type": "string"
-    },
-    "enabled": {
-      "default": true,
-      "type": "boolean"
-    },
-    "features": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "interval": {
-      "enum": [
-        "month",
-        "quarter",
-        "year",
-        "one_time",
-        "donation"
-      ],
-      "title": "TierPriceInterval",
-      "type": "string"
-    },
-    "interval_display": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "currency",
-    "amount_cents",
-    "interval"
-  ],
-  "title": "TierPricesAttributesItem",
-  "type": "object"
-}

removedInput schema / properties / prices_attributes / type
```
Removed value: -"array"
```

First observedv2.0.0Oct 3, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description still adds value by naming the auth scope (tiers:write) and the confirm-gate behavior, plus 'changes account state', which is context the annotations alone do not spell out.

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

Conciseness4/5

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

Two short, front-loaded sentences with no filler, and the confirm/auth requirements come after the purpose statement in the right order. The opening 'Create a tier.' largely restates the title, costing a little.

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, non-idempotent mutation with 8 params and nested objects but no output schema, the description covers confirm and auth but says nothing about what is returned or how the payload/payload_file alternatives relate to the body flags. Adequate but with clear gaps.

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

Parameters3/5

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

Schema coverage is 63%, so several nested fields (prices_attributes items, name/description at top level, payload vs body-flag mutual exclusion) are undocumented. The description's confirm note duplicates the schema's own description of that field and adds no meaning for the remaining parameters, so it lands at the baseline.

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?

States a specific verb+resource ('Create a tier') that an agent can act on immediately. It does not explicitly distinguish itself from the sibling replace_tier/update_tier, so sibling differentiation is left to inference from the verb.

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

Usage Guidelines3/5

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

Names two preconditions: confirm=true for the user-requested action and the tiers:write OAuth scope. However, it gives no guidance on when to create versus replace_tier or update_tier, which are the most confusable siblings.

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

Deploy Server

Create a tier

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools