Skip to main content
Glama

BRAINIAC Website Conversion Intelligence

Detect landing page drop-off

conversion-intelligence_landing-page-dropoff-detect

Rank supplied pages by measured exit rate from views and exits. Rates use only caller counts and do not claim why visitors left. Price $0.04 USDC. POST /api/v1/conversion-intelligence/landing-page-dropoff-detect. 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_landing-page-dropoff-detect"
  }
}

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/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful extras — the $0.04 USDC price, the POST endpoint, and 402 on unpaid calls — and warns that rates are count-based with no causal claim. However, it says nothing about what the response contains, how the 14 input channels are interpreted, or what happens on insufficient data, which is a significant gap for a paid, mutation-free analysis call.

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?

Four short sentences, front-loaded with the core ranking behavior, followed by the causation caveat and then billing/transport facts. Nothing is padded, though the endpoint path repeats the tool name and could be trimmed.

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 14-parameter tool with nested objects and no annotations or output schema, the description omits input-format selection and return-shape expectations. It does cover pricing, transport, and the analytical caveat, so it is partially complete but not sufficient to call the tool confidently without reading the schema.

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, many nested, so the description must compensate. It only hints that the caller supplies page views and exits, giving no meaning for the csv/json/text/file input alternatives, minSample, forms, fields, events, stages, segments, or expectedEvents.

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?

The description states a specific verb and metric — rank supplied pages by measured exit rate computed from views and exits — which cleanly separates it from siblings such as form-abandonment-analyze that work on starts/completes. It does not explicitly name which sibling to use instead, but the scope is unmistakable.

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 metric definition (rank pages by exit rate), so an agent can infer the appropriate situation. There is no explicit when-to-use/when-not guidance and no referral to an alternative sibling, leaving routing to inference.

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