Skip to main content
Glama
Daemon-Killer

google-activity-assistant

by Daemon-Killer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_activityA
Search the user's ingested Google activity by keyword (full-text).

Args:
    query: Keywords to match against titles/URLs/channels (FTS5).
           Use empty string with filters to list recent activity.
    product: Optional filter: search | youtube | maps | chrome | assistant | play | other
    start_date: Optional ISO date/time lower bound (e.g. 2024-01-01)
    end_date: Optional ISO date/time upper bound (e.g. 2024-12-31)
    limit: Max hits (1–100, default 20)
get_activity_statsA

Return counts and date range for the local activity database. Use this to check whether Takeout data has been imported and which products exist.

get_db_infoA

Return local DB path and whether the file exists (no Google network calls).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search_activity performs full-text search, get_activity_stats provides aggregate counts and date range, and get_db_info returns local database metadata. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: search_activity, get_activity_stats, get_db_info. The naming is predictable and uniform.

Tool Count4/5

With 3 tools, the set is at the lower end of the typical range but each tool serves a necessary role for the server's purpose: searching, understanding the dataset, and checking database state. It feels slightly thin but not unreasonable.

Completeness4/5

The domain is searching Google activity data. The set covers the core need (search), provides statistical overview (stats), and exposes database status (db_info). There are minor gaps such as no explicit ability to list all products or fetch a single record by ID, but these are workable via the existing tools.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources