Conecto

Count a website's visits

analytics_add_site

Start counting visits to a website, like Plausible or Umami: add the returned snippet to every page, before . It uses no cookies and keeps no IP addresses. When a visitor becomes a contact through Conecto's chat, a booking, a form or a newsletter signup, the visit that brought them is kept with their contact. Custom events: conecto("Signup", {"plan": "pro"}) in the page, with revenue as a third argument ({revenue: 49.9, currency: "USD"}), or define them without touching the site (analytics_define_events). It also counts on its own clicks on links to other sites, phone and email links, file downloads, form submissions, searches on the site, pages that answer an error, elements with data-conecto-event="Name", and Conecto's own chats, bookings, forms and signups that start on the site; and keeps clicks and scrolling for heatmaps and the pages' Core Web Vitals. analytics_install has the steps for Shopify, WordPress and others. $3 a month with 100,000 events, renewed from the balance; the first month is this call. Costs $3.00 per call; nothing if it fails.

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": {
      "domain": "<domain>"
    },
    "name": "analytics_add_site"
  }
}

Input Schema

Name	Required	Description
`name`	No
`domain`	Yes	The site, e.g. halversoncycle.example (www. and other subdomains count too).
`time_zone`	No	The days of the stats; the business calendar's time zone if left out.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare the mutation/safety profile; the description adds substantial context beyond that: no cookies and no stored IPs, visit-to-contact attribution when a visitor converts, a long list of auto-tracked interactions (outbound links, tel/mailto, downloads, form submissions, error pages, data-conecto-event elements, heatmaps, Core Web Vitals). It also discloses cost terms — "$3 a month with 100,000 events... Costs $3.00 per call; nothing if it fails" — which no annotation conveys.

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

Conciseness3/5

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

The purpose is correctly front-loaded and the closing cost line is valuable, but the middle is a run-on semicolon chain enumerating every auto-tracked interaction type, which is far more than needed to select and call the tool. The tracking inventory and the inline code sample could be trimmed or deferred to documentation.

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?

With no output schema, the description usefully signals a return value ("the returned snippet") and explains the post-call install step, billing, and downstream attribution — enough to call it correctly. Minor gaps: nothing on what happens if the domain is already registered, and no ownership/verification requirement for the domain.

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 67% (domain and time_zone are documented in the schema, name is not), so the schema already does most of the work. The description never addresses the parameters directly — it never explains what `name` is for or how `time_zone` affects day boundaries beyond what the schema says — so it adds no meaning here. Baseline 3 is appropriate.

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?

"Start counting visits to a website" is a specific verb + resource, and the second clause ("add the returned snippet to every page, before </head>") makes the concrete outcome unmistakable. It also names siblings it is not (analytics_install, analytics_define_events), so an agent can separate site creation from install steps or event definitions without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description routes explicitly to alternatives: analytics_install "has the steps for Shopify, WordPress and others" and events can be defined "without touching the site (analytics_define_events)". The condition for the custom-events path (in-page code vs. API definition) is stated, not implied.

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

All Conecto tools Inspect

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

Need Help?