Skip to main content
Glama

Add contact

contacts_add
Idempotent

Adds one contact, or merges tags into an existing one. Uses no send quota. ONLY add a person who agreed to receive marketing email from this business (for example they signed up, or the person you are helping confirms they opted in). If you are not sure, ask first. Addresses that unsubscribed, bounced or complained cannot be re-added. Not reversible through these tools (there is no delete tool), so check the email is right. Requires API key scope: contacts.

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": {
      "email": "<email>",
      "consent": "<consent>"
    },
    "name": "contacts_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags to add, for example ["vip"]. Merged with existing tags.
emailYesThe contact email address.
consentYesMust be true. Confirms this person agreed to receive marketing email from this business. Never set it on a guess.
last_nameNoLast name.
first_nameNoFirst name, used for personalization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial detail beyond the annotations: no send quota consumed, ineligibility of previously unsubscribed/bounced/complained addresses, irreversibility because no delete tool exists, and the required API key scope 'contacts'. The idempotentHint=true annotation is corroborated by the tag-merge behavior, so nothing conflicts.

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?

Purpose is front-loaded in the first clause, followed by quota, consent policy, eligibility exclusions, and reversibility warnings in a logical order. Dense but every sentence carries operational weight; only the repeated caution about getting the email right could be folded into the consent sentence.

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

Completeness5/5

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

For a non-destructive but irreversible write tool with no output schema, the definition covers permissions, side effects, eligibility constraints, and failure modes, which is everything an agent needs before calling. No return-value explanation is needed since no output schema is declared.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description goes beyond and explains the policy behind the required `consent` boolean (recorded opt-in, ask first, never guess) rather than restating its type. The email-accuracy warning also adds meaning to the `email` parameter that the schema's format constraint does not convey.

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?

States a specific verb and resource ('Adds one contact') and immediately clarifies the dual behavior ('or merges tags into an existing one'), which is non-obvious from the name alone. The scope ('one contact') and the upsert semantics let an agent distinguish it from a search or bulk-import operation without inspecting the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides unusually explicit eligibility rules: only add people who agreed to marketing email, ask if unsure, and never re-add unsubscribed/bounced/complained addresses. It lacks an explicit pointer to an alternative tool (e.g. contacts_search) for the case where the contact already exists, which keeps it from a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources