Skip to main content
Glama

Manage Contacts Batch

manage_contacts_batch
Destructive

Batch create, update, or delete Google contacts in one call. Save time by managing multiple contact records together instead of one-by-one.

Instructions

Batch create, update, or delete contacts. Consolidated tool replacing batch_create_contacts, batch_update_contacts, and batch_delete_contacts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldNoFor "update" action — the single People API field to update across all contacts in this batch. Required. Must be one of: names, phoneNumbers, emailAddresses, organizations, nicknames, urls, userDefined, relations, biographies, addresses, birthdays. Using a single field per batch call prevents unintentional data loss from a union updateMask overwriting unrelated fields.
actionYesThe action to perform: "create", "update", or "delete".
updatesNoList of update dicts for "update" action. Each dict must contain contact_id and may contain the same fields as contacts.
contactsNoList of contact dicts for "create" action. Each dict may contain: given_name, family_name, phones, emails, organizations, notes, address. Deprecated: phone, email, organization, job_title.
contact_idsNoList of contact IDs for "delete" action.
user_google_emailYesThe user's Google email address. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already disclose the destructive, non-read-only, non-idempotent nature, and the description adds no behavioral context beyond the bare operations. Important caveats about update overwrite risk and field-specific behavior appear only in the schema, not in the description.

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?

Two concise sentences with no filler. It front-loads the core action and provides consolidation context, though it is slightly terse for a complex batch mutation tool.

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?

The schema and annotations carry most of the necessary context, including per-parameter semantics and destructive behavior. However, the description does not provide a high-level overview connecting actions to their required inputs (contacts vs updates vs contact_ids), which would help an agent plan a batch operation safely.

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?

Schema description coverage is 100% and each parameter has detailed descriptions, including action enums, field constraints, and which parameter applies to which action. The description adds no parameter information, but none is needed given the thorough schema.

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 states a specific verb ('Batch create, update, or delete contacts') and a resource, clearly indicating the tool's consolidated purpose. It distinguishes itself from the replaced batch_* tools, though it does not explicitly contrast with current siblings like manage_contact.

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 guidance is given on when to use this batch tool versus the singular manage_contact, nor which action requires which parameter set. The phrase 'Consolidated tool replacing...' references tools that are no longer in the sibling list, so it provides little actionable routing for an agent.

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

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/WorldCentralKitchen/google_workspace_mcp'

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