Skip to main content
Glama
thenavidm

Beehiiv MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Accept ad offer

create_ad_network_offer
Destructive

Accepts an ad network offer and inserts the selected advertisement into a publication post; set confirm=true to authorize this state-changing action.

Instructions

Accept ad offer. Changes account state and requires confirm=true for the user-requested action. OAuth integrations require posts:write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoNamed private account from BEEHIIV_ACCOUNTS. Defaults to BEEHIIV_DEFAULT_ACCOUNT or the first configured account.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete JSON body instead of individual body flags. Supports nullable fields and nested bulk structures. Cannot be combined with body flags or payload_file.
post_idNoThe ID of the post where the advertisement should be inserted.
offer_idNoThe ID of the ad offer to accept.
custom_introNo
payload_fileNoLocal JSON request body file, at most 5 MB. Contents are validated before the API call and are never logged.
publication_idYesThe prefixed ID of the publication object
advertisement_idNoThe ID of the advertisement creative to use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv3.0.1
    • addedInput schema / $defs
      Added value: +{
+  "custom_intro": {
+    "description": "Plain text displayed before the advertisement. Maximum 200 characters and cannot contain URLs. Available only when custom ad introductions are enabled for the publication.",
+    "type": "string"
+  }
+}
    • 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 / custom_intro / $ref
      Added value: +"#/$defs/custom_intro"
    • removedInput schema / properties / custom_intro / description
      Removed value: -"Plain text displayed before the advertisement. Maximum 200 characters and cannot contain URLs. Available only when custom ad introductions are enabled for the publication."
    • removedInput schema / properties / custom_intro / type
      Removed value: -"string"
    • addedInput schema / properties / payload / properties / custom_intro / $ref
      Added value: +"#/$defs/custom_intro"
    • removedInput schema / properties / payload / properties / custom_intro / description
      Removed value: -"Plain text displayed before the advertisement. Maximum 200 characters and cannot contain URLs. Available only when custom ad introductions are enabled for the publication."
    • removedInput schema / properties / payload / properties / custom_intro / type
      Removed value: -"string"
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructive/not-read-only/non-idempotent, but the description adds genuinely new context: it mutates account state, demands explicit confirm for the exact requested action, and names the OAuth scope (posts:write). It does not note reversibility or rate limits, keeping it at a 4.

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?

Three terse sentences, front-loaded with the action, then the safety requirement, then the auth requirement. No filler.

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

Completeness4/5

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

For a 9-parameter, nested-payload mutation with no output schema, the description covers the critical call-shaping facts (confirm gate, auth scope, state change). It omits the payload-vs-body-flags/payload_file mutual exclusion, though the schema itself documents that.

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 89%, so parameters such as offer_id, advertisement_id, post_id, confirm, and payload are already well documented in the schema. The description adds no parameter-level syntax or format detail beyond that, so the baseline 3 applies.

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 ('Accept ad offer') that an agent can immediately distinguish from read siblings like list_ad_network_offers. However, it never names the counterpart read tool or the related ad_network_offers_advertisements, so sibling routing is left to inference.

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?

The confirm=true clause ('only when the user asked for exactly this action') gives useful invocation context, but the description offers no when-not guidance, no prerequisites, and no mention of the alternative offer-listing tool. Usage is implied rather than spelled out.

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