Skip to main content
Glama

Read a lead magnet

get_lead_magnet
Read-onlyIdempotent

Read one lead magnet: its landing page texts, form settings, public URL, the email form embed code for the user's own site, when its PDF was made, and a readiness report (blocking problems that stop it going live, and advisory ones worth fixing, such as no cover image or a CTA button with no link). Every lead magnet is gated: visitors leave an email and consent before they get the PDF.

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": "get_lead_magnet"
  }
}

Input Schema

NameRequiredDescriptionDefault
magnetIdYesFrom list_lead_magnets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world, non-destructive behavior, so the description only needed to add context and it does: it explains that every lead magnet is gated behind an email-and-consent form, and it distinguishes blocking readiness problems from advisory ones. It stops short of saying what happens for an unknown or unpublished magnetId.

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?

It leads with the action, then lists the payload, then closes with the gating rule that explains why the form data matters. The single long sentence is dense but nearly every clause carries distinct information; only the embed-code clause is slightly verbose.

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 must convey return values, and it does so item by item, including the shape of the readiness report and the gating model. Missing only error/empty-case behavior, which is a minor gap for a single-id read.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains magnetId and its origin in list_lead_magnets. The description adds no format, length, or sourcing detail beyond that, which is the baseline expectation when the schema does the work.

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?

"Read one lead magnet" pairs a specific verb with the resource, and the enumeration (landing page texts, form settings, public URL, embed code, PDF creation date, readiness report) makes the returned surface concrete. It does not name a sibling it is not, so an agent still has to infer the boundary against get_lead_magnet_performance.

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?

Usage is implied by the singular "one lead magnet" and the retrieval framing, but there is no explicit statement of when to pick this over get_lead_magnet_performance or update_lead_magnet. The prerequisite chain (magnetId from list_lead_magnets) lives only in the schema, not the description.

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