Skip to main content
Glama

Traffic and Google data

get_traffic
Read-only

Traffic of the brand's site from the connected Google accounts. view: ai_referrals = visits and revenue AI assistants send; search_console = clicks, impressions, queries, pages and opportunities; analytics = GA4 sessions, sources and pages (account-wide). Read-only. Replies with metrics carry glossary: the dashboard's own explanation of each one.

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_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPeriod in days: 7, 28 (default) or 90.
viewNoWhat to return (default ai_referrals).
brandNoBrand id, name or domain (from get_account (view: brands)). Optional when the account has a single brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/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 the 'Read-only' sentence is largely redundant. The description does add real behavior beyond the annotations: the data originates from connected Google accounts, the analytics view is account-wide rather than brand-scoped, and responses carry a glossary explaining each metric.

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?

Front-loaded with the core statement, then a compact semicolon-separated view list that maps directly to the enum values. Only waste is the 'Read-only' clause duplicating the annotation and slightly awkward phrasing around the glossary sentence.

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 3-parameter, no-output-schema read tool, the definition covers the source, the view semantics, the account-wide scope caveat and the presence of a glossary in responses. It does not describe response shape or ordering, which carries some weight given there is no output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description meaningfully expands the terse 'view' enum documentation by spelling out what each of the three values actually returns. The days and brand parameters are left entirely to the schema, which is acceptable given their clarity.

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 (the brand's site traffic) and a specific source (connected Google accounts), then enumerates the three views with concrete metrics for each. It is clear what the tool returns, though it does not explicitly distinguish itself from lookalike siblings such as get_visibility.

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 per-view breakdown (ai_referrals = visits and revenue from AI assistants; search_console = clicks, impressions, queries, pages, opportunities; analytics = GA4 sessions, sources, pages) gives an agent enough context to pick the correct view. It stops short of saying when not to use this tool or naming a sibling alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.