Skip to main content
Glama
Sign In
@lodd/mcp-server

@lodd/mcp-server

by hholen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_conversion_pages

Identify pages that precede a specific conversion event, showing conversion rate and average time to convert, to find high-converting content.

Instructions

Find which pages lead to a specific conversion event. Shows pages viewed before the event in the same session, with conversion rate and average time to convert. Useful for identifying high-converting content.

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": {
      "site": "<site>",
      "event_name": "<event_name>"
    },
    "name": "get_conversion_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite domain or UUID
limitNoMax results (1-1000)
periodNoTime period30d
event_nameYesThe conversion event name (e.g. 'signup_click', 'purchase')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.15

TDQS

A4/5.0
Behavior4/5

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

No annotations provided; description clearly states what data is returned (pages, conversion rate, time to convert) and the session context. Lacks details on auth or rate limits but covers the main behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences: purpose, details, usefulness. No redundancy, front-loaded, efficient.

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

Completeness4/5

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

Describes core functionality and metrics well, but lacks explicit output structure (e.g., list of objects). Given no output schema, slightly more detail would help, but still adequate.

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%, so baseline 3. Description adds context about the output (conversion rate, time) but does not explain parameter syntax or constraints beyond schema.

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?

Clear verb 'find' and resource 'pages leading to a specific conversion event'. Distinguishes from siblings like get_pages and get_events by focusing on conversion attribution.

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?

Implied usage for identifying high-converting content, but no explicit comparison to alternatives like get_funnel or get_event_sequences, and no when-not-to-use guidance.

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

Deploy Server

Other Tools