Conecto

Break an event or goal down

analytics_breakdown

Read-onlyIdempotent

One event or goal by a prop (by: "prop:plan") or by where its visits came from: channel, source, referrer, campaign, medium, term, content, landing_page, page, country, device, browser or os. Each row has conversions, visitors, the conversion rate (for where visits came from) and revenue, so you see which channels, campaigns and landing pages bring signups and money, including what analytics_track and Conecto's own bookings, chats and forms counted. 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>"
    },
    "name": "analytics_breakdown"
  }
}

Input Schema

Name	Required	Description	Default
`by`	No		channel
`to`	No	With period custom: the last day.
`from`	No	With period custom: the first day, 2026-10-01.
`goal`	No
`site`	Yes	The site's domain (e.g. halversoncycle.example) or its site_id.
`event`	No
`limit`	No
`period`	No		30d
`filters`	No	Narrow 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.

First observedOct 28, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful context by explaining the row-level output metrics and that results include analytics_track and Conecto bookings/chats/forms data, but it does not clarify pagination/limit behavior, default time handling, or other operational details.

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 description is dense and somewhat run-on, packing dimensions, output metrics, data sources, and a 'Free' note into a short span. It front-loads the core behavior, but some repetition between the dimension list and the later 'channels, campaigns and landing pages' phrase weakens structure.

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

Completeness3/5

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

There is no output schema, and the description does describe the returned row metrics, which is important. However, for a tool with 9 parameters, nested filters, and a 44% schema description coverage, it still omits important context around period/date behavior, limit handling, and whether event or goal is expected despite neither being required.

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 only 44%, so the description needs to compensate. It does explain the custom property syntax for `by` and lists many dimension values for breakdown/filtering, but it leaves `period`, `limit`, and the exact event-vs-goal parameter semantics underdescribed.

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 states a specific operation: breaking down one event or goal by a property or acquisition dimension. It lists concrete dimensions and output metrics, so the agent can understand what the tool produces. It does not explicitly distinguish itself from siblings such as analytics_stats or analytics_funnel, which keeps it from a 5.

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 use case by saying it shows which channels, campaigns, and landing pages bring signups and money. However, it does not explicitly say when to choose this tool over analytics_stats, analytics_funnel, or analytics_paths, nor does it provide when-not guidance.

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?