ga4-seo-mcp

Overview Schema Source Related Servers Discussions Admin

traffic_sources

Read-only

Retrieve top GA4 source/medium entries with sessions, active users, and conversions to identify which channels drive site performance.

Instructions

Top traffic sources (source / medium) with sessions, active users and conversions.

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": {
      "property_id": "<property_id>"
    },
    "name": "traffic_sources"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`date_end`	No	today
`date_start`	No	7daysAgo
`property_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. Still, the description says nothing about default behavior beyond what the schema shows, no row-limit behavior, no note that it queries live GA4 data, and the listed metrics duplicate information available in the output schema.

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?

A single front-loaded sentence with the resource first and the returned metrics last. No filler, no redundancy.

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?

An output schema exists, so return values needn't be explained, and the safety annotations are adequate. However, with zero parameter documentation and no usage guidance, an agent still lacks enough to invoke this correctly for a 4-parameter reporting tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description carries the full burden and fails: it never mentions property_id, the date range, the 7-day default, or what limit controls. The phrase 'top' only loosely implies a limit parameter.

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?

States a specific resource and scope: top traffic sources broken down by source/medium, with the metrics returned (sessions, active users, conversions). This is clearly distinguishable from siblings like top_pages or conversions_summary, though it never explicitly names those alternatives.

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 gives no when-to-use guidance, no exclusions, and no mention of how it relates to run_report or the other summary tools. The agent must infer that this is a pre-built report from the name alone.

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