Skip to main content
Glama
ktibbs9417

GAM MCP Server

by ktibbs9417
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_gmail_log_events

Retrieve Gmail log events with optional filters for actor, date range, or event name, and export results to a Google Sheet.

Instructions

    Retrieves Gmail log events and optionally writes them to a Google Sheet.
    
    Args:
        actor_email: Optional email to filter logs for a specific actor.
        start_date: Optional start date (YYYY-MM-DD).
        end_date: Optional end date (YYYY-MM-DD).
        event_name: Optional event name to filter.
        output_sheet_id: Optional Sheet ID for output. Strongly recommended.
        output_sheet_name: Tab name for sheet output.
        
    GAM pattern:
        gam report gmail [actor <actor_email>] [start <start_date>]
            [end <end_date>] [event <event_name>] [todrive ...]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNo
event_nameNo
start_dateNo
actor_emailNo
output_sheet_idNo
output_sheet_nameNoGmail Logs

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations provided; description does not disclose read-only nature, authentication requirements, rate limits, or effects of missing output_sheet_id. Only hints at output recommendation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description includes an Args list and GAM pattern. The pattern adds useful context but increases length; could be more succinct. Structure is adequate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists but description doesn't clarify return values or behavior (e.g., empty results, errors). Lacks completeness for a tool with 6 optional parameters.

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?

Schema coverage is 0%, but the description lists each parameter with a brief functional description (e.g., 'Optional email to filter logs'), adding value beyond the bare schema.

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 clearly states the tool retrieves Gmail log events and optionally writes to a Google Sheet, with specific verb and resource. It distinguishes from sibling audit tools by focusing on Gmail logs.

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?

No explicit guidance on when to use this tool versus siblings like run_gam_command or audit tools. The description implies usage through parameters but lacks context or alternatives.

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/ktibbs9417/gamcp'

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