Skip to main content
Glama
Sign In

Matomo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Matomo Visit Summary

matomo_visit_summary
Read-onlyIdempotent

Return Matomo visits, unique visitors, actions, bounce rate, visit duration, and conversions for a site and period. Answers how traffic volume and engagement changed.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "yesterday",
      "period": "day",
      "_apiKey": "anonymous",
      "site_id": 1,
      "_baseUrl": "https://demo.matomo.cloud/"
    },
    "name": "matomo_visit_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate, relative date, or range such as 2026-07-01,2026-07-31
periodYes
_apiKeyYesMatomo read-only auth token
segmentNoOptional Matomo segment expression
site_idYesMatomo website ID
_baseUrlYesHTTPS Matomo installation URL, such as https://example.matomo.cloud/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the list of returned metrics and the kind of question it answers, but does not disclose additional behavioral details such as response shape, date handling, or limitations.

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?

Two short sentences with no filler. The first sentence states exactly what is returned and for what scope; the second explains the analytic use case. Every word earns its place.

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?

For a read-only summary tool, the description lists the key metrics and the question it answers, while the schema covers parameter details. There is no output schema, but the description gives a sufficient mental model of what the tool returns. It could be slightly more explicit about how 'changed' is represented, but overall it is 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 83%, so the schema already documents most parameters. The description only loosely maps to 'site and period' via site_id and period/date, adding little semantic meaning beyond what the input schema provides.

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 uses a specific verb ('Return') and a clear resource: Matomo visits, unique visitors, actions, bounce rate, visit duration, and conversions. It also states the analytic purpose ('Answers how traffic volume and engagement changed'), which distinguishes it from sibling tools focused on goals, pages, or referrers.

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

Usage Guidelines4/5

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

The description conveys a clear context for use: answering questions about traffic volume and engagement for a site and period. It does not explicitly name alternatives or exclusion criteria, but the use case is evident enough for an agent to choose this over the more specialized Matomo sibling tools.

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

All Matomo 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