Skip to main content
Glama
googleanalytics

Google Analytics MCP Server

Official

get_account_summaries

Retrieve Google Analytics account and property information to view available data sources and manage access permissions.

Instructions

Retrieves information about the user's Google Analytics accounts and properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_account_summaries' tool, decorated with @mcp.tool() which handles both implementation and registration. It asynchronously retrieves all account summaries using the Google Analytics Admin API client and converts them to dictionaries.
    @mcp.tool()
    async def get_account_summaries() -> List[Dict[str, Any]]:
        """Retrieves information about the user's Google Analytics accounts and properties."""
    
        # Uses an async list comprehension so the pager returned by
        # list_account_summaries retrieves all pages.
        summary_pager = await create_admin_api_client().list_account_summaries()
        all_pages = [
            proto_to_dict(summary_page) async for summary_page in summary_pager
        ]
        return all_pages
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Retrieves information,' implying a read-only operation, but doesn't cover aspects like authentication needs, rate limits, error handling, or what specific data is returned. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 directly states the tool's purpose without any fluff or redundancy. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, with no annotations and sibling tools present, it lacks context on when to use it and behavioral details, making it incomplete for optimal agent decision-making.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is assigned as it meets expectations for a parameterless tool without redundancy.

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 verb ('Retrieves') and resource ('information about the user's Google Analytics accounts and properties'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_property_details' or 'run_report', which might retrieve similar or overlapping data, so it falls short of a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention context, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone. This lack of explicit guidance reduces its effectiveness in tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googleanalytics/google-analytics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server