Pixelesq

Get site analytics

get_site_analytics

Read-only

Get site traffic analytics: visits, page views, bounce rate and visit length with the change against the previous period, visits per day, and the top pages, sources, devices, locations and browsers

Input Schema

Name	Required	Description	Default
`period`	No	Time period for analytics	LAST_30_DAYS
`projectId`	Yes	The project ID

Output Schema

Name	Required	Description
`kpis`	No	Visits and page views per day over the period
`note`	No	Which window the top lists cover, when it is not the chosen period
`counts`	No
`period`	No
`topPages`	No
`topDevices`	No
`topSources`	No
`topBrowsers`	No
`topLocations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "counts": {
+      "additionalProperties": {},
+      "properties": {
+        "avgDuration": {
+          "additionalProperties": {},
+          "properties": {
+            "change": {
+              "type": "number"
+            },
+            "current": {
+              "type": "number"
+            },
+            "formatted": {
+              "type": "string"
+            },
+            "previous": {
+              "type": "number"
+            },
+            "trend": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "bounceRate": {
+          "additionalProperties": {},
+          "properties": {
+            "change": {
+              "type": "number"
+            },
+            "current": {
+              "type": "number"
+            },
+            "previous": {
+              "type": "number"
+            },
+            "trend": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "pageviews": {
+          "additionalProperties": {},
+          "properties": {
+            "change": {
+              "type": "number"
+            },
+            "current": {
+              "type": "number"
+            },
+            "previous": {
+              "type": "number"
+            },
+            "trend": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "visits": {
+          "additionalProperties": {},
+          "properties": {
+            "change": {
+              "type": "number"
+            },
+            "current": {
+              "type": "number"
+            },
+            "previous": {
+              "type": "number"
+            },
+            "trend": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "kpis": {
+      "description": "Visits and page views per day over the period",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "pageviews": {
+            "type": "number"
+          },
+          "visits": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Which window the top lists cover, when it is not the chosen period",
+      "type": "string"
+    },
+    "period": {
+      "type": "string"
+    },
+    "topBrowsers": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "browser": {
+            "type": "string"
+          },
+          "hits": {
+            "type": "number"
+          },
+          "visits": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "topDevices": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "device": {
+            "type": "string"
+          },
+          "hits": {
+            "type": "number"
+          },
+          "visits": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "topLocations": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "hits": {
+            "type": "number"
+          },
+          "location": {
+            "type": "string"
+          },
+          "visits": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "topPages": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "hits": {
+            "type": "number"
+          },
+          "pathname": {
+            "type": "string"
+          },
+          "visits": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "topSources": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "hits": {
+            "type": "number"
+          },
+          "referrer": {
+            "type": "string"
+          },
+          "visits": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety and scope are covered. The description adds the useful behavioral detail that each metric includes a comparison against the previous period, but says nothing about project scoping, empty-data behavior, or cost/latency, which matters for an aggregate-report call.

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?

A single front-loaded sentence with no filler; the metric inventory is dense but each item is informative. The trailing enumeration is long but earns its place by telling the agent what it will receive.

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?

Return shape is covered by an output schema and parameters are fully documented in the schema, so the description need not repeat them. What remains missing is routing guidance relative to the sibling analytics tools, which is the main gap for an otherwise simple read tool.

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 100%, including the period enum and its default, so the schema carries parameter meaning. The description never mentions the period parameter or how the comparison window derives from it, adding no meaning beyond the schema.

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?

Specific verb and resource ('Get site traffic analytics') followed by an enumeration of the exact metrics returned, so an agent knows precisely what data comes back. It does not explicitly contrast with the nearby analytics siblings (get_ai_referral_analytics, get_search_performance), leaving that differentiation to be inferred from the metric names.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. With three analytics tools in the sibling list, an agent gets no help deciding between traffic analytics, AI referral analytics, and search performance.

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

All Pixelesq 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?