Skip to main content
Glama
Sign In
seocrawl-mcp

seocrawl-mcp

Official
by SEOcrawl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_ga4_traffic_by_source

Retrieve Google Analytics 4 sessions by source/medium or default channel grouping, including share percentage for each traffic source.

Instructions

GA4 sessions by source/medium or default channel grouping, with share %.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ga4_traffic_by_source"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It only states the basic function without disclosing read-only nature, authentication requirements, rate limits, or any side effects. The lack of behavioral context is a significant gap.

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 very concise at 10 words, but it is single-sentence and lacks structure (no sections, no examples). It is efficient but incomplete.

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

Completeness2/5

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

With no output schema, no annotations, and an empty input schema, the description is too minimal. It does not explain the return format, how 'share %' is computed, or how to specify the grouping dimension. The tool complexity is low but the context is insufficient.

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?

The input schema is empty with additionalProperties true, implying no fixed parameters. However, the description suggests parameters to select grouping (source/medium or channel grouping) but does not define them. This creates confusion between the implied parameter need and the actual 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?

The description clearly states the tool returns GA4 sessions organized by source/medium or default channel grouping, including share percentage. It is specific about the resource and the type of breakdown.

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 guidance is provided on when to use this tool versus siblings like get_ga4_summary or compare_ga4_date_ranges. There is no mention of prerequisites or when not to use it.

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

Deploy Server

Other Tools