Skip to main content
Glama
dipseth

google-workspace-unlimited

manage_people_contact_labels

Add or remove contacts from a Google contact label. Provide the action ('label_add' or 'label_remove'), emails, and label name to manage group membership.

Instructions

Manage Google People contact labels (contact groups) for one or more emails. Supports 'label_add' to ensure contacts exist and attach them to a label, and 'label_remove' to detach matching contacts from a label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
labelNo
actionYes
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
errorNoError message if operation failed
actionYesAction that was performed: 'label_add' or 'label_remove'
messageNoHuman-readable summary of the operation result
successYesWhether the operation completed successfully
label_nameYesName of the contact group/label that was managed
batch_errorsNoNumber of batch API operations that encountered errors
failed_emailsNoList of email addresses that failed to process
contacts_createdNoNumber of new contacts that were created (for label_add action)
emails_processedNoTotal number of email addresses that were processed
contacts_existingNoNumber of existing contacts found (for label_add action)
contacts_modifiedNoNumber of contacts that were added to or removed from the label
contacts_not_foundNoNumber of emails with no matching contacts (for label_remove action)
label_resourceNameNoResource name/ID of the contact group
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It mentions that 'label_add' ensures contacts exist, but does not discuss behavior for missing labels, error handling, or permission requirements.

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?

Two efficient sentences with no redundant information, front-loading the tool's purpose.

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 presence of an output schema, the description covers the primary intent but lacks details on parameter combinations, default behaviors, and edge cases, leaving agents potentially underinformed.

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?

Only 25% of schema properties have descriptions (only user_google_email). The description adds meaning for email ('one or more emails') and action ('supports label_add and label_remove'), but does not elaborate on the label parameter or user_google_email beyond the 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 it manages Google People contact labels (contact groups) for one or more emails, specifying two actions: 'label_add' and 'label_remove'. This distinguishes it from read-only sibling tools like list_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?

The description indicates the two actions but does not explicitly state when to use this tool over alternatives, nor provide prerequisites or when not to use it.

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