Skip to main content
Glama

Create a lead magnet from a PDF

create_lead_magnet_from_pdf
Destructive

Make a PRIVATE draft lead magnet from an existing PDF at a public web address (no login), or with magnetId replace the PDF of a lead magnet made from a PDF (same address, leads and numbers). The plan's file size limit applies. Nothing is public until publish_lead_magnet; replacing a LIVE one's PDF first returns the change to confirm (confirmLiveChange) and needs magnets:publish. Use PDFs the user owns.

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": {
      "url": "<url>"
    },
    "name": "create_lead_magnet_from_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA public https:// address of the PDF (no login).
magnetIdNoTo replace the PDF of an existing lead magnet made from a PDF (same address, leads and numbers).
confirmLiveChangeNoReplacing the PDF of a LIVE lead magnet changes what visitors get: call first without it, then with true after the user agrees.

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?

Beyond the annotations (destructiveHint=true, openWorldHint=true, readOnlyHint=false), the description discloses the real behavioral risks: output is only a PRIVATE draft, replacing a LIVE magnet's PDF is gated behind a confirmation round-trip and the magnets:publish scope, and it preserves 'same address, leads and numbers'. Return behavior and what happens on failure are not described.

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?

Purpose is front-loaded in the first sentence, followed by the replace mode and then the safety constraints; there is no filler. Density is high and phrases like 'same address, leads and numbers' are terse enough to be slightly ambiguous.

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 destructive, 3-parameter mutation with no output schema, the description is nearly complete: modes, permission requirement, size limit, and confirmation protocol are all covered. The notable gap is that it never says what comes back (presumably a magnet identifier needed for publish_lead_magnet) or how size/URL errors surface.

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 description coverage is 100%, so the schema already explains url, magnetId, and the two-step confirmLiveChange flow. The description largely restates the same semantics ('same address, leads and numbers', the confirm-first pattern) rather than adding new meaning beyond the structured fields.

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 gives a specific verb and resource ('Make a PRIVATE draft lead magnet from an existing PDF at a public web address') and explicitly separates the create path from the replace path via magnetId. It also disambiguates from publish_lead_magnet ('Nothing is public until publish_lead_magnet'), though other creation siblings such as a generic lead-magnet or ebook-from-url creator are never contrasted.

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

Usage Guidelines5/5

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

Explicit branch conditions are given: omit magnetId to create, supply magnetId to replace a PDF-made magnet, and 'call first without it, then with true after the user agrees' for confirmLiveChange. Prerequisites are also stated — public https address with no login, ownership of the PDF, and the plan's file size limit.

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