Skip to main content
Glama
logly-uk

Logly MCP server

Official
by logly-uk

logly_funnels

List conversion funnels defined for a site, showing funnel IDs and step sequences for user journey analysis.

Instructions

List the conversion funnels defined for a site, with their IDs and step sequences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesLogly site ID (slug). Call logly_list_sites to discover it.

Implementation Reference

  • index.js:91-96 (handler)
    The tool 'logly_funnels' handler function. It takes a site ID and calls the Logly API endpoint /api/sites/{site}/funnels to list conversion funnels defined for a site, returning their IDs and step sequences.
    tool(
      "logly_funnels",
      "List the conversion funnels defined for a site, with their IDs and step sequences.",
      { site: siteArg },
      ({ site }) => loglyApi(`/api/sites/${encodeURIComponent(site)}/funnels`)
    );
  • index.js:91-96 (registration)
    The tool is registered using a custom 'tool' helper function (defined at line 37) which wraps server.tool() from the MCP SDK. The registration includes the name 'logly_funnels', description, input schema (site string), and the handler.
    tool(
      "logly_funnels",
      "List the conversion funnels defined for a site, with their IDs and step sequences.",
      { site: siteArg },
      ({ site }) => loglyApi(`/api/sites/${encodeURIComponent(site)}/funnels`)
    );
  • Input schema for 'logly_funnels': requires a single 'site' parameter (string, described as 'Logly site ID (slug)') sourced from the shared siteArg constant defined at line 47.
    tool(
      "logly_funnels",
      "List the conversion funnels defined for a site, with their IDs and step sequences.",
      { site: siteArg },
      ({ site }) => loglyApi(`/api/sites/${encodeURIComponent(site)}/funnels`)
    );
  • index.js:8-27 (helper)
    The 'loglyApi' helper function is used by the handler to make authenticated HTTP requests to the Logly API. It reads the LOGLY_API_KEY from environment, builds the URL with query parameters, and returns the response text.
    async function loglyApi(path, params) {
      const key = process.env.LOGLY_API_KEY;
      if (!key) {
        throw new Error(
          "LOGLY_API_KEY is not set. Create one in Logly → Settings → API keys."
        );
      }
      const url = new URL(BASE + path);
      for (const [k, v] of Object.entries(params || {})) {
        if (v !== undefined && v !== null && v !== "") url.searchParams.set(k, String(v));
      }
      const res = await fetch(url, {
        headers: { Authorization: `Bearer ${key}`, Accept: "application/json" },
      });
      const text = await res.text();
      if (!res.ok) {
        throw new Error(`Logly API ${res.status} on ${path}: ${text.slice(0, 300)}`);
      }
      return text;
    }
Behavior3/5

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

Since annotations are absent, the description must fully disclose behavior. It indicates the tool lists funnels and returns IDs and steps, which is appropriate for a read operation. However, it does not mention any side effects, permissions, or rate limits, leaving some uncertainty.

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?

The description is a single sentence of 14 words, conveying all necessary information without redundancy. It is front-loaded and efficient.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, no output schema), the description sufficiently covers what the tool does and what it returns. No additional context is needed.

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

Parameters4/5

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

The input schema already describes the 'site' parameter with 100% coverage. The description adds value by suggesting calling logly_list_sites to discover the site ID, which aids the agent beyond the 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?

The description explicitly states the verb 'List', the resource 'conversion funnels for a site', and the output 'with their IDs and step sequences'. This clearly differentiates from sibling tools like logly_funnel_results or logly_events.

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 is provided on when to use this tool versus siblings, nor any conditions or prerequisites beyond the required site parameter. The description does not mention exclusions or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly-uk/logly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server