Skip to main content
Glama

Publish a lead magnet

publish_lead_magnet
DestructiveIdempotent

Make a draft or paused lead magnet PUBLIC on the user's Library and return its URL and the email form embed code. Only call this when the user has asked to publish. It first checks readiness and refuses with the reasons if something blocks it (no Library address, plan limit). If the ebook was edited after the PDF was made, the PDF is rendered again first unless refreshPdf is false.

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": {
      "magnetId": "<magnetId>"
    },
    "name": "publish_lead_magnet"
  }
}

Input Schema

NameRequiredDescriptionDefault
magnetIdYesFrom list_lead_magnets or create_lead_magnet.
refreshPdfNoWhen the ebook was edited after the PDF was made, publishing stops and asks first. Then send true to make the PDF again from the ebook as it is now, or false to publish the existing PDF as it is. Ask the user which.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description explains the mechanism behind them: the magnet becomes publicly visible and an email form goes live. It adds failure-mode detail the annotations cannot carry — a pre-publish readiness check that refuses with reasons (no Library address, plan limit) — plus the PDF re-render sequencing. It stops short of saying whether a published magnet can be reverted or how exposure is scoped, which would be the last piece for a destructive write.

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?

Front-loaded with the action and its outputs, then the gating rule, then the edge case — a sensible order with no filler. The final sentence overlaps noticeably with the refreshPdf property description, so it is efficient rather than perfectly tight.

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?

With no output schema, the description names what comes back (URL and embed code) and enumerates the two blocking conditions, which is what an agent needs to handle failure. It does not cover permissions or what the embedded form looks like on success, but nothing essential for correct invocation is missing.

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 100% and the refreshPdf property already documents the stop-and-ask behavior, so the description is largely restating it. It does add the ordering detail (the PDF is rendered again before publishing, not after), which is marginal value on top of a fully documented schema — baseline 3.

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

Purpose5/5

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

States a specific verb and state transition (draft/paused -> PUBLIC) on a named resource (lead magnet in the user's Library) and declares the outputs (URL and email form embed code). The state precondition implicitly separates it from unpublish_lead_magnet, so an agent can route without opening schemas.

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

Usage Guidelines4/5

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

"Only call this when the user has asked to publish" is an explicit gating rule, and the refreshPdf sentence tells the agent to stop and ask the user rather than guessing. It does not name a sibling alternative (e.g. update_lead_magnet or unpublish_lead_magnet), so the routing guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources