google-workspace-mcp

contacts_create

Add a contact to your Google account with their name, email, phone, organization, and title.

Instructions

Create a new contact with name, email, phone, organization, and title.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "given_name": "<given_name>"
    },
    "name": "contacts_create"
  }
}

Input Schema

Name	Required	Description	Default
`email`	No
`phone`	No
`title`	No
`given_name`	Yes
`family_name`	No
`organization`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior, but it only restates the mutation intent. It does not mention required permissions, idempotency, behavior on duplicate contacts, or what the response contains, which is a significant gap for a create operation.

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?

The description is a single, front-loaded sentence that directly states the action and lists fields. It is appropriately concise with no wasted words, though it could have used the space to clarify required fields or parameter specifics.

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?

Given the tool has 6 parameters, 0% schema description coverage, and no annotations, the description is insufficient. It omits family_name, does not clarify the required given_name, and provides no context on contact creation behavior, uniqueness, or relationship to batch operations, making it difficult for an agent to use correctly without external knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the parameters. It mentions 'name' (which is ambiguous between given_name and family_name), email, phone, organization, and title, but omits family_name entirely. 'Title' is also ambiguous (job title vs. honorific), and no formats or constraints are clarified.

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 clearly states the action ('Create a new contact') and lists the key fields (name, email, phone, organization, title), making the purpose understandable. However, it does not differentiate from sibling tools like contacts_batch_create, which also creates contacts.

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 provided on when to use this tool instead of alternatives such as contacts_batch_create, contacts_update, or contacts_search. There are no usage conditions, prerequisites, or exclusions mentioned, leaving the agent without context for tool selection.

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

Deploy Server