gsuite

google-contacts_delete_contact

Delete a contact permanently from Google Contacts. Provide the contact's resource name to remove it without recovery.

Instructions

Delete a contact permanently

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": {
      "resourceName": "<resourceName>"
    },
    "name": "google-contacts_delete_contact"
  }
}

Input Schema

Name	Required	Description	Default
`resourceName`	Yes	Resource name of the contact to delete (e.g., 'people/c1234567890')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Jul 13, 2026

TDQS

B3.3/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. It discloses that deletion is permanent, but lacks information on side effects (e.g., impact on group memberships), undo possibility, authorization requirements, or error handling.

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?

Extremely concise—a single, well-structured phrase. No unnecessary words, and the core action is front-loaded.

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 simple delete operation with one parameter and no output schema, the description is adequate but lacks crucial details like error states, idempotency, or whether the operation is irreversible (though 'permanently' suggests it). It meets the minimum but leaves gaps.

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 coverage is 100% and the parameter 'resourceName' already has a clear description. The tool description adds no additional semantic value 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 'Delete a contact permanently' clearly states the verb (delete) and resource (contact), and distinguishes from sibling tools like create_contact or update_contact. The word 'permanently' adds finality.

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 on when to use this tool versus alternatives. It does not mention preconditions (e.g., whether the contact must exist) or when not to use it (e.g., if soft delete is preferred).

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