Skip to main content
Glama

Visibility Genies

Read the organic overview

get_google_analytics_organic_overview
Read-only

Organic Search totals from Google Analytics for a date range next to the range just before it, with a daily or weekly trend. Read only and free.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_google_analytics_organic_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
trendNoGrain of the trend series.daily
deviceNoOnly this device: desktop, mobile or tablet.
countryNoOnly this country, as its two-letter ISO code, for example DE.
endDateNoInclusive date as YYYY-MM-DD. Give both startDate and endDate, or neither for the last 28 complete property days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoInclusive date as YYYY-MM-DD. Give both startDate and endDate, or neither for the last 28 complete property days.
pageContainsNoOnly pages whose address contains this text, in any case. Not for site search or ecommerce by item.

Output Schema

NameRequiredDescriptionDefault
errorNo
quotaNo
trendNo
sourceNo
statusYes
currentNo
requestNo
previousNo
warningsNo
comparisonNo
diagnosticsNo
reportMetadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so "Read only" is largely redundant; "free" does add genuinely new context given projectId is described as billed. The prior-period comparison and daily/weekly trend are real behavioral disclosures, but return shape, row limits, and empty-data behavior are left to 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?

Two sentences, front-loaded with what the tool returns, then behavior (comparison), then cost/safety. No filler, and every clause carries information an agent can act on.

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?

With an output schema present, return values need not be explained, and annotations plus the full schema coverage handle safety and parameters. What is missing is routing guidance among the many GA siblings and any hint that the result can be sliced by device, country, or page substring.

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%, with every parameter including defaults, ISO code format, and the last-28-complete-days fallback documented in the schema itself. The description adds no meaning beyond that baseline and does not surface the device, country, or pageContains filters at all.

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?

"Organic Search totals from Google Analytics" plus the comparison period and trend grain gives a specific verb-free but precise statement of what data comes back. It is distinguishable from page-level siblings like get_google_analytics_organic_landing_pages, but it never names an alternative, so differentiation is inferred from the word "totals" rather than stated.

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?

There is no explicit when-to-use guidance: nothing says to pick this for a high-level organic summary rather than traffic_acquisition, traffic_breakdown, or page_performance. The only implicit signal is that the output is aggregate totals with a prior-period comparison, which an agent must reason about on its own.

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.

Resources