Skip to main content
Glama
Sign In
SEOctopus

SEOctopus

by itsjwill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analytics_overview

Get sessions, users, bounce rate, top pages, and traffic sources from Google Analytics for a specified GA4 property and date range.

Instructions

Get Google Analytics overview: sessions, users, bounce rate, top pages, sources

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

Input Schema

NameRequiredDescriptionDefault
propertyIdYesGA4 property ID
dateRangeNoDate range: last7days, last28days, last90days, lastYear, or YYYY-MM-DD:YYYY-MM-DDlast28days
compareWithNoCompare with: previousPeriod or previousYear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears full burden for behavioral disclosure. It only lists output metrics without mentioning read-only nature, rate limits, or data aggregation details, leaving significant gaps.

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?

The description is a single, efficient sentence that conveys purpose and key output metrics without any superfluous information.

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 3 parameters and no output schema, the description lists output metrics but does not specify the structure or format of the response, leaving moderate ambiguity for an agent.

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% with descriptions for all 3 parameters. The tool description adds no further parameter context beyond what the schema provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and resource ('Google Analytics overview'), and lists key metrics (sessions, users, bounce rate, top pages, sources), clearly differentiating it from sibling tools like analytics_pages or analytics_realtime.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives (e.g., analytics_pages for page-specific data, analytics_traffic for traffic sources). The usage is implied but not contrasted with siblings.

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