Skip to main content
Glama

delete_contact

DestructiveIdempotent

Delete a Google Contacts entry by resourceName to remove an unwanted contact from your account.

Instructions

Delete a contact from Google Contacts by resourceName.

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": "delete_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceNameYesContact resourceName to delete (e.g. 'people/c123456789')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds only that deletion targets a specific Google Contacts resource by resourceName; it says nothing about irreversibility, permission requirements, or behavior when the resourceName doesn't exist, so it adds modest value beyond the structured fields.

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 front-loaded sentence with the verb, resource, and targeting key in that order. Nothing redundant or filler-laden.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter destructive tool whose annotations fully declare the safety profile and whose schema is fully documented, the description covers enough to call it correctly. Minor gaps remain around error/not-found behavior and confirmation expectations, which the annotations only partly imply.

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?

With a single parameter at 100% schema description coverage including an example value ('people/c123456789'), the schema carries the parameter meaning on its own. The phrase "by resourceName" in the description merely restates the schema, so baseline 3 applies.

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 ("Delete a contact from Google Contacts") plus the identifying key (resourceName), so the agent knows exactly what operation this performs. It does not explicitly contrast itself with siblings like update_contact or upsert_contact, which keeps it short of a 5.

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?

There is no guidance on when to use this versus alternatives such as update_contact or upsert_contact, and no preconditions (e.g., resolve the contact first via search_contacts, confirm the resourceName is current). The agent must infer usage entirely from the tool name.

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