Skip to main content
Glama
dipseth

google-workspace-unlimited

Manage Gmail Allow List

manage_gmail_allow_list
Idempotent

Manage a trust list of emails to bypass Gmail confirmation prompts. Also add or remove emails from People contact labels.

Instructions

Manage the workspace trust list stored in GMAIL_ALLOW_LIST and related People contact labels. Supports 'add', 'remove', 'view' for the Gmail/Chat trust list and 'label_add', 'label_remove' for People contact labels. Trust entries can be single emails, lists, or comma-separated strings; group specs ('group:', 'groupId:') are resolved via the People API. Trusted recipients/targets skip elicitation confirmation for Gmail sending operations today and (in future) selected Chat operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoEmail address(es) or group specs to add/remove. Supports: Single email ('user@example.com'), List of emails (['user1@example.com', 'user2@example.com']), Comma-separated string ('user1@example.com,user2@example.com'), Group specs ('group:Team Name', 'groupId:contactGroups/123'). Required for add/remove/label_add/label_remove actions, ignored for view action.
labelNoPeople contact group/label name for label_add/label_remove actions (e.g., 'Work Team', 'AI Tribe'). Required when action is 'label_add' or 'label_remove', ignored for other actions.
actionYesAction to perform: 'add' (add entries to trust list), 'remove' (remove entries from trust list), 'view' (show current trust list), 'label_add' (add emails to People contact label), 'label_remove' (remove emails from People contact label)
user_google_emailNoUse 'me' or 'myself' for auto-resolution to authenticated user, or provide specific email address. If None, uses current authenticated user (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses group resolution via People API, effect on elicitation confirmation, and future Chat operations. Annotations provide idempotentHint but description adds value without contradiction.

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

Conciseness4/5

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

Single dense paragraph front-loads purpose and actions. Efficient but could be broken into clearer sections; still earns its place.

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 full schema coverage and output schema present, description covers functionality well. Could add error handling details but complete enough for selection.

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 100%, baseline 3. Description adds meaning by explaining group spec syntax, user_google_email auto-resolution, and action enum context, justifying a 4.

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?

Describes managing the trust list and People labels, lists five actions. Clearly specifies verb+resource but does not explicitly differentiate from sibling tools like manage_gmail_label or manage_people_contact_labels.

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?

Implies usage for managing trust list to skip confirmation, but does not explicitly state when to use vs. alternatives or provide exclusion criteria.

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/dipseth/google_workspace_fastmcp2'

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