Skip to main content
Glama

Linq.es MCP Server

List Captured Leads

list_leads
Read-onlyIdempotent

Retrieves contact submissions (name, email, phone, message, campaign tag, and timestamp) captured via a Linq.es profile's Lead Magnet form, up to 'limit' records. When to use: choose this to inspect audience signups, newsletter subscribers, and contact inquiries submitted on a profile; use get_profile_analytics instead for anonymous traffic, referrer, and click metrics. Prerequisites: requires Bearer lnq_live_ Pro authentication and an owned 'profile' handle (call list_profiles first if unknown; returns an empty list if Lead Capture has not yet received submissions). Validation: returns isError: true if 'profile' is empty or not owned by the caller; 'limit' defaults to 50, values <= 0 reset to 50, and values > 200 clamp to 200. Side effects: read-only and idempotent; modifies no stored records (returned objects contain contact PII owned by the user). Returns: JSON text with {profile, count, leads: [{id, profile, formTitle, campaign, name, email, phone, message, createdAt}]}.

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": {
      "profile": "<profile>"
    },
    "name": "list_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of captured leads to return between 1 and 200 (defaults to 50 when omitted or <= 0; values above 200 are clamped to 200).
profileYesOwned Linq.es profile handle whose Lead Magnet form submissions should be returned (e.g. 'alex').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / default
      Added value: +50
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of recent leads to return (default: 50, max: 200)"New value: +"Maximum number of captured leads to return between 1 and 200 (defaults to 50 when omitted or <= 0; values above 200 are clamped to 200)."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / profile / description
      Previous value: -"Profile handle to fetch captured leads for"New value: +"Owned Linq.es profile handle whose Lead Magnet form submissions should be returned (e.g. 'alex')."
    • addedInput schema / properties / profile / minLength
      Added value: +1
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial context beyond them: error behavior when 'profile' is empty or unowned, limit defaulting and clamping, empty-list behavior before Lead Capture has data, and a note that returned objects contain user-owned contact PII. That is exactly the kind of operational detail annotations cannot convey.

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?

Labeled sections (When to use, Prerequisites, Validation, Side effects, Returns) make it scannable and front-load the purpose. It is dense and repeats the limit clamping already in the schema, which keeps it just short of a 5.

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?

No output schema exists, but the description supplies the exact JSON return shape ({profile, count, leads: [...]}) including nested field names, and covers auth, ownership validation, and empty-state behavior. Nothing an agent needs in order to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the limit semantics (default 50, <=0 reset, >200 clamp) are already in the schema, so that portion is largely repeated. The description does add meaning the schema lacks: the profile must be owned by the caller and a validation failure returns isError: true, which clarifies the string parameter's real constraint.

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 ("Retrieves contact submissions... captured via a Linq.es profile's Lead Magnet form") and enumerates the returned fields, so the agent knows exactly what comes back. It also explicitly distinguishes itself from get_profile_analytics, which covers anonymous traffic rather than identified signups.

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?

Contains an explicit "When to use" block naming the audience-signup/newsletter/contact-inquiry scenarios and names get_profile_analytics as the alternative for traffic and click metrics. Prerequisites are spelled out too (Bearer lnq_live_<key> Pro auth, owned profile handle, list_profiles first if unknown).

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.