Skip to main content
Glama

BRAINIAC Website Conversion Intelligence

Analyze an analytics funnel

conversion-intelligence_analytics-funnel-analyze

Calculate stage-to-stage conversion rates and drop-offs from supplied funnel counts. Missing counts are not filled in, and a drop-off is not treated as a proven cause. Price $0.04 USDC. POST /api/v1/conversion-intelligence/analytics-funnel-analyze. Unpaid calls return 402 and do not run.

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": "conversion-intelligence_analytics-funnel-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
formsNo
pagesNo
eventsNo
fieldsNo
stagesNo
funnelsNo
sourcesNo
segmentsNo
minSampleNo
expectedEventsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a fair job: it discloses the pricing model ($0.04 USDC), the transport (POST to a specific path), the failure mode for unpaid calls (402 and no execution), and two important analytical semantics — missing counts are not imputed and drop-offs are not treated as causal. What it omits is the shape of the returned analysis, but the payment/error disclosure is genuinely beyond-schema value.

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?

Three compact sentences with the core purpose front-loaded, followed by analytical caveats and then commercial/transport facts. No filler; the endpoint string and price are dense but operationally necessary given no annotations.

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

Completeness2/5

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

For a tool with 14 optional inputs, nested objects, no annotations, and no output schema, the description never explains which input channel to use or how the arrays relate (e.g., that stages supply the funnel counts that drive the calculation). It is under-specified relative to the complexity of the call surface.

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

Parameters2/5

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

Schema description coverage is 0% across 14 parameters, several of them nested arrays (stages, pages, events, forms, sources, segments), so the description must compensate and largely does not. Only 'funnel counts' hints at the input domain; csv/json/text/file alternatives, minSample, expectedEvents, and the per-entity count fields are left entirely to field names and constraints.

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?

States a concrete verb and resource: 'Calculate stage-to-stage conversion rates and drop-offs from supplied funnel counts.' That distinguishes it reasonably from sibling analyses like form-abandonment or landing-page drop-off, though it never names an alternative explicitly.

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?

'From supplied funnel counts' implies the tool consumes caller-provided data rather than fetching it, which is useful selection context. However, there is no explicit statement of when to prefer this over segment-compare, event-coverage-check, or the other sibling analyzers, and no prerequisites are spelled out.

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