Skip to main content
Glama

List lead magnets

list_lead_magnets
Read-onlyIdempotent

List the workspace's lead magnets (draft, live or paused) with their public URLs, lead counts and whether their ebook changed since the PDF was made (stale), plus the Library's address and the plan's limits. A lead magnet is the PUBLISHED form of an ebook: a PDF snapshot of the saved ebook plus a landing page with an email form on the workspace's Library (https://.unplain.page). Editing the ebook never changes the public PDF until it is refreshed. Use this first whenever the user names a lead magnet, guide or their Library.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_lead_magnets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return. Defaults to 25.
searchNoCase-insensitive text matched against the title and slug.
statusNoOnly lead magnets in this state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real domain behavior beyond them: the draft/live/paused state model, the stale-vs-fresh distinction, and the crucial caveat that 'Editing the ebook never changes the public PDF until it is refreshed.' It also surfaces the Library URL template, which an agent needs to present results meaningfully.

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 verb and the returned fields, then a definitional paragraph, then the usage directive, so the key information comes first. It is longer than strictly necessary — the ebook/PDF explanation is educational rather than operational — but every sentence is informative and none is filler.

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

Completeness5/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 takes on the job of enumerating return values and does so explicitly (URLs, lead counts, stale status, Library address, plan limits). For a zero-required-parameter read tool, an agent has everything needed to call it and to interpret the response.

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% with all three parameters documented (limit default 25, case-insensitive search over title and slug, status enum), so the schema carries parameter meaning. The description only indirectly reinforces the status filter by enumerating the three states, adding no syntax or edge-case detail beyond the schema. Baseline 3 applies.

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 resource ('List the workspace's lead magnets') plus the exact payload returned: public URLs, lead counts, stale flag, Library address and plan limits. It also defines what a lead magnet IS (published PDF snapshot of an ebook plus a landing page), which cleanly separates it from the ebook-oriented and singular get_lead_magnet siblings.

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?

The closing sentence gives explicit routing guidance: 'Use this first whenever the user names a lead magnet, guide or their Library', which implicitly establishes this as the discovery step that must precede get_lead_magnet or update_lead_magnet. It stops short of naming those siblings or stating exclusions (e.g. when to skip straight to search or performance), so it is strong but not complete.

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