Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Google Analytics properties

imports_ga4_properties
Read-onlyIdempotent

The Google accounts connected for the site's Google Analytics import, and the properties each one can read. Use a propertyId (properties/123) in imports.start. When nothing is connected, give the person links.connectGoogleAnalytics. Admin.

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": {
      "siteId": "<siteId>"
    },
    "name": "imports_ga4_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds the genuinely new bits: this requires Admin, and the agent should hand back a connect link when the list is empty. Return content (accounts and their readable properties) is also characterized, which annotations cannot express.

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?

Three short sentences, front-loaded with what is returned, then the action to take with the result, then the fallback. Nothing is padded or repeated, and the telegraphic 'Admin.' still reads clearly as a permission requirement.

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 no output schema, the description carries the return-shape burden and does so by naming accounts plus their readable properties and the propertyId form. The main residual gap is the siteId input, which is undocumented here and in the schema.

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 0% for the single siteId parameter, and the description never names siteId or explains its format, only implying site scoping via 'the site's Google Analytics import'. The properties/123 detail is useful but describes a value consumed by imports.start, not an input to this tool.

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 names the resource precisely: connected Google accounts for the site's Analytics import plus the properties each can read. The verb is implied ('list'), but the resource and scope are unambiguous and clearly distinct from the analytics_get*Properties siblings, which surface analytics data rather than connected accounts.

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?

It gives a concrete downstream use ('Use a propertyId (properties/123) in imports.start') and a conditional branch when no accounts exist ('give the person links.connectGoogleAnalytics'). It does not say when to prefer this over imports_list or imports_sources, so alternatives are left implicit.

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