Skip to main content
Glama

google-contacts_create_contact

Create a new contact in Google Contacts by specifying fields such as name, email, phone, address, organization, and more.

Instructions

Create a new contact with specified fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsNoArray of URL objects with value, type, etc.
namesNoArray of name objects with givenName, familyName, displayName, etc.
sourcesNoSources to create the contact in (default: 'CONTACT')
addressesNoArray of address objects with formattedValue, type, etc.
birthdaysNoArray of birthday objects with date information
biographiesNoArray of biography objects with value, contentType, etc.
personFieldsYesComma-separated list of fields to return (e.g., 'names,emailAddresses,phoneNumbers,addresses,organizations')
phoneNumbersNoArray of phone number objects with value, type, etc.
organizationsNoArray of organization objects with name, title, etc.
emailAddressesNoArray of email address objects with value, type, etc.
Behavior2/5

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

No annotations are present, so the description must fully disclose behavioral traits. It fails to mention any side effects, prerequisites, permissions, or limitations beyond the basic create action.

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?

The description is a single concise sentence that directly states the tool's purpose without unnecessary words.

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?

Despite high schema coverage, the description lacks information about the return value or behavior of the tool, which is important for a create operation. With no output schema, the agent is left guessing about the response structure.

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% with detailed parameter descriptions. The tool description adds no additional meaning beyond what the schema already provides.

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 the action (Create) and resource (new contact) with the ability to specify fields, which is distinct from sibling operations like update, delete, get, list, and search.

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 versus alternatives (e.g., when to create vs. update). The description does not specify contexts or exclusions.

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/w-10-m/gsuite'

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