Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

See where people drop off

analytics_funnel
Read-onlyIdempotent

How many visitors did each step in order (pages and events, 2 to 8), the share kept at each step, how many dropped, and the median time between steps. Steps happen in order on the same day; anything may happen between them. Free.

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>",
      "steps": "<steps>"
    },
    "name": "analytics_funnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoWith period custom: the last day.
fromNoWith period custom: the first day, 2026-10-01.
siteYesThe site's domain (e.g. halversoncycle.example) or its site_id.
stepsYesEach a page ("/pricing", * for any part), an event name ("Signup"), or {"page"|"event", "props", "name"}.
periodNo30d
filtersNoNarrow the stats: page and entry_page ("/blog/*", * for any part), goal (a goal's name), event, channel (Direct, Organic search, Paid search, Organic social, Paid social, AI assistants, Email, Referral, Affiliates, Display, Paid other, Other campaigns), source ("Google", "Direct"), referrer, campaign, medium, term, content, country ("DE"), device (desktop, tablet, mobile), browser, os. Example: {"channel": "Organic search", "device": "mobile"}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds meaningful behavioral context beyond that: steps are evaluated in order on the same day, unrelated events may occur between steps, the returned metrics are listed, and the tool is free to use.

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 compact and front-loads the core purpose and returned metrics. The ordering constraint follows logically, and 'Free' is short and relevant, though the overall paragraph format could be slightly more structured.

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?

Given the absence of an output schema, the description usefully names the returned metrics and explains the key funnel evaluation rule. The detailed input schema and annotations cover most remaining parameter and safety context, making this reasonably complete for an agent to call the tool correctly.

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 high at 83%, so the schema already documents most parameters thoroughly, including filters and step formats. The description reinforces that steps are pages and events with a 2-to-8 limit, but adds little parameter meaning beyond what the schema 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?

The description clearly identifies a funnel analysis tool, naming the exact metrics returned: visitors per ordered step, share kept, drop-off, and median time between steps. It is specific enough to distinguish it from general analytics tools, but it does not explicitly contrast itself with siblings such as analytics_paths or analytics_breakdown.

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?

The description implies the tool is for ordered multi-step conversion analysis and adds the constraint that steps occur on the same day. However, it gives no explicit guidance on when to choose this over analytics_paths, analytics_stats, or analytics_breakdown, and no exclusions or prerequisites are stated.

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

All Conecto toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources