Skip to main content
Glama

create_contact

Create a new Google Contacts entry with names, emails, phone numbers, addresses, notes, and photos so you can add contact details directly.

Instructions

Create a brand-new contact in Google Contacts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoWebsite or profile URLs (strings or { value, type })
notesNoBiography or notes about the contact
emailsNoEmail addresses (strings or { value, type: 'work'|'home'|'other' })
phonesNoPhone numbers (strings or { value, type: 'mobile'|'work'|'home'|'other' })
prefixNoHonorific prefix (e.g. Dr., Mr., Ms.)
suffixNoHonorific suffix (e.g. Jr., III, PhD)
birthdayNoBirthday in YYYY-MM-DD or MM-DD format
fullNameNoFull display name (automatically split if givenName/familyName are omitted)
jobTitleNoJob title or role
nicknameNoNickname
addressesNoPhysical addresses (strings or structured address objects)
givenNameNoFirst / given name
photoPathNoOptional local file path to a PNG/JPG photo to set as the contact's avatar
departmentNoDepartment within the organization
familyNameNoLast / family name
middleNameNoMiddle name
photoBase64NoOptional base64-encoded PNG/JPG photo to set as the contact's avatar
customFieldsNoCustom key-value pairs stored on the contact
organizationNoCompany or organization name
groupResourceNamesNoContact group resource names (e.g. ['contactGroups/myContacts'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety and idempotency profile is covered structurally. The description adds little beyond reinforcing that this is a creation, and does not mention duplicate handling, permission/auth requirements, or what is returned.

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?

A single short sentence with no wasted words, front-loading the verb and resource. There is nothing to trim.

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?

For a 20-parameter creation tool with zero required fields and no output schema, the description leaves open how a minimally-specified contact behaves (e.g. fullName splitting, empty-name handling) and how duplicates are treated versus upsert_contact. The annotation- and schema-rich context keeps this from being a serious gap, but it is not fully complete.

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 all 20 parameters are documented in the schema, so the description does not need to restate them. Baseline 3 is appropriate since the one-line description adds no parameter-level meaning, such as name-splitting behavior or photo precedence.

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 and resource ("Create a brand-new contact in Google Contacts"), and the word "brand-new" signals it differs from update/upsert. It stops short of naming the sibling alternatives upsert_contact or update_contact, so an agent must infer the boundary itself.

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?

"Brand-new" implies use this only when the contact does not exist, but there is no explicit when-to-use/when-not guidance and no mention of upsert_contact or update_contact as the alternatives. The presence of both upsert_contact and update_contact siblings makes that omission meaningful.

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