Skip to main content
Glama

Get lead magnet performance

get_lead_magnet_performance
Read-onlyIdempotent

Visitors, form starts, new leads (submissions), conversion rate, downloads and reading numbers for the workspace's lead magnets over 7, 30 or 90 UTC days or all time: totals per lead magnet and summed, and optionally daily series, traffic sources, campaigns, read-through by page and clicked links. Use it to answer how lead magnets perform and to compare them. Every result includes definitions: state them when they matter (for example, visitors are counted per day, not as unique people). Aggregates only; it never returns who the leads are.

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

Input Schema

NameRequiredDescriptionDefault
rangeNoWhole UTC days ending today. 'all' totals have no start date; its daily series covers at most 365 days.30d
includeNoExtra detail per lead magnet. daily: visitors and submissions per UTC day. sources / campaigns: top 20 utm_source (else referring site, else direct) / utm_campaign, with visitors and submissions. readThrough: readers still reading at each page (opted-in readers only). links: top clicked links in the PDF. Omit for totals only.
magnetIdsNoLead magnets to report (from list_lead_magnets). Default: every one that is not a draft, up to 20.

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 already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description then adds genuinely useful behavior beyond that: every result carries `definitions`, and results are aggregates only with no lead identities returned, setting a hard privacy boundary. Remaining gaps (response shape, max-size/pagination) are minor given the closed, read-only nature.

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?

The metrics enumeration is front-loaded, followed by usage, a caveat about `definitions`, and the aggregate-only boundary. Dense but every clause carries information; the metric list is long but appropriate for describing what a performance report returns.

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 does the work of explaining that results are per-magnet totals plus an optional breakdown set, which is enough to invoke and interpret. Parameter behavior is fully schema-documented, so an agent has what it needs before calling, though the exact response field structure beyond totals is only loosely implied.

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%, so the enum values, defaults and per-value meanings of range/include are already documented in the schema. The description largely restates that surface (7/30/90 UTC days or all time; optional daily series, sources, campaigns, read-through, links) without adding format or behavior detail the schema lacks, so 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?

Names a specific verb-and-resource pair (report on lead magnet performance) and enumerates the metrics returned: visitors, form starts, new leads, conversion rate, downloads, reading numbers. It is clearly the analytics read tool, distinct from sibling get_lead_magnet (single config) and list_lead_magnets (enumeration, which it references for magnetIds).

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?

"Use it to answer how lead magnets perform and to compare them" gives clear context for selection, and the reference to list_lead_magnets for IDs helps routing. It stops short of explicit when-not-to-use guidance or naming a sibling to prefer for single-magnet configuration details.

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