Launch Engine

Overview Schema Source Related Servers Discussions Admin

funnel_optimize

Read-only

Optimize conversion rates by running tests across your sales funnel for a specific market. Get data-driven suggestions to improve performance.

Instructions

Funnel Optimization Engine — CRO testing across the conversion funnel.

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": {
      "market_name": "<market_name>"
    },
    "name": "funnel_optimize"
  }
}

Input Schema

Name	Required	Description	Default
`market_name`	Yes	The market/pipeline slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false, but the description uses 'testing,' which could imply mutation. The description does not clarify that the tool is read-only or describe any behavioral traits beyond what annotations provide. Potential ambiguity between 'testing' and 'analysis' is not resolved.

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 description is a single concise sentence, efficiently conveying the tool's domain. However, it is front-loaded with 'Funnel Optimization Engine' which is redundant with the name, but overall structure is clean and minimal.

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?

Given the simple parameter set and available annotations, the description is insufficient. It does not explain the type of output (e.g., report, recommendations) or confirm that the tool is read-only. A more complete description would clarify what the user receives from running this optimization engine.

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% with a clear description for 'market_name' ('The market/pipeline slug'). The tool description adds no additional meaning or context to the parameter beyond what the schema already provides.

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?

Description states it's a 'Funnel Optimization Engine' for 'CRO testing across the conversion funnel.' This clearly indicates the tool focuses on conversion rate optimization testing specifically for funnels. While it distinguishes from general testing tools like 'creative_test' or 'rapid_test', it does not explicitly differentiate from other funnel-related tools.

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?

No guidance on when to use this tool versus alternatives. No prerequisites, exclusions, or context for appropriate usage are provided. The description only states the tool's purpose without any usage direction.

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