Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Landing Page CRO, CTA, Form Field & Funnel Analyzer

analyze_landing_page_cro_funnel
Read-onlyIdempotent

Audit landing pages for headline clarity, form friction, CTA hierarchy, social proof, and A/B testing scripts to identify conversion funnel issues and prioritize CRO fixes.

Instructions

Audit landing page headlines, form field friction, CTA hierarchy, social proof density, and A/B testing scripts (VWO, Optimizely, PostHog) ($0.80/1k).

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": {
      "urls": "<urls>"
    },
    "name": "analyze_landing_page_cro_funnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesLanding page URLs to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the cost model ($0.80/1k) and the specific third-party script vendors (VWO, Optimizely, PostHog) that will be detected. It does not state rate limits, how many URLs can be batched, or what happens with unreachable pages.

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?

A single dense sentence with the verb and audit dimensions front-loaded and cost appended as a trailing qualifier. Every clause carries content; nothing is repeated from the title.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, single-parameter audit tool, the description covers scope and pricing, but with no output schema present it gives no sense of what the report contains (scores, issue lists, pass/fail) or how results are structured. Batch-size behavior for the URL array is also unaddressed.

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% for the single 'urls' array parameter, so the schema already carries the meaning. The description adds nothing about URL format, batch size limits, or whether subpages are followed, so baseline 3 applies.

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?

Names a specific verb ('Audit') and an enumerated set of resources (headlines, form fields, CTA hierarchy, social proof, A/B testing scripts), which clearly separates it from generic SEO or funnel-detection siblings. It stops short of explicitly differentiating itself from the closest neighbors (e.g., audit_technical_seo_broken_links), but the enumeration of CRO-specific checks makes the scope unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The enumerated audit categories imply the use case, but the agent must infer it entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.