SEOctopus

Overview Schema Source Related Servers Discussions Admin

analytics_traffic

Get traffic breakdown by source, medium, or channel for a GA4 property to analyze marketing performance and channel effectiveness.

Instructions

Get traffic breakdown by source, medium, or channel

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": {
      "propertyId": "<propertyId>"
    },
    "name": "analytics_traffic"
  }
}

Input Schema

Name	Required	Description	Default
`propertyId`	Yes	GA4 property ID
`dateRange`	No	Date range	last28days
`dimension`	No	Traffic dimension to group by	channel

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only describes the output but does not disclose behavioral traits such as whether the operation is read-only, side effects, authentication needs, or performance implications. For a data retrieval tool, minimal safety context is missing.

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 a single, front-loaded sentence that is concise and directly states the purpose. It earns its place but could be more informative without losing brevity.

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?

Given the tool has 3 parameters and no output schema, the description is minimally complete for a simple query. It could benefit from indicating the return format or typical usage, but it covers the basic purpose.

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 100%, so each parameter (propertyId, dateRange, dimension) has a description in the schema. The tool description adds little beyond what the schema already conveys, such as the dimension enum values. Baseline 3 is appropriate.

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 'Get traffic breakdown by source, medium, or channel' clearly states the verb (Get), resource (traffic breakdown), and mentions the grouping options from the dimension parameter. However, it does not differentiate from sibling tools like analytics_overview or analytics_pages, which also deal with traffic data.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or when not to use it, leaving the agent without decision support for tool selection.

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