Skip to main content
Glama

create_contact

Add a single contact with email, name, tags, and custom fields, recording consent to email. Only add opted-in addresses to maintain sender reputation and comply with CAN-SPAM/GDPR.

Instructions

Add a single contact. Adding a contact records consent to email them — only add addresses that opted in, or the send will damage sender reputation and may breach CAN-SPAM/GDPR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoSegmentation tags
emailYesContact email address
phoneNoPhone number (max 50 chars)
sourceNoWhere this contact came from (max 100 chars)
companyNoCompany name (max 150 chars)
job_titleNoJob title (max 100 chars)
last_nameNoLast name (max 100 chars)
first_nameNoFirst name (max 100 chars)
custom_fieldsNoCustom key-value attributes
Behavior5/5

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

The description adds significant behavioral context beyond the annotations: adding a contact records consent to email them, and misuse can damage sender reputation and breach CAN-SPAM/GDPR. This is a critical constraint that is not captured by readOnlyHint, openWorldHint, idempotentHint, or destructiveHint, and it directly informs the agent's decision making.

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 composed of two concise sentences. The first sentence states the core function, and the second adds a crucial warning. No filler or redundancy; every word contributes to clarity and safety guidance.

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?

Given the tool's complexity (9 parameters, nested objects), the schema handles parameter documentation well. The description covers the key usage context and the most critical behavioral caveat (consent). It does not mention duplicate handling or return value, but the idempotentHint annotation (false) and the absence of an output schema mean these are less critical for selection/correct invocation.

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 coverage is 100%, so the schema already documents all parameters. The description enriches the semantics of the 'email' parameter by clarifying that providing an email implies recorded consent, which is a legal implication not stated in the schema. Other parameters (tags, custom_fields, etc.) remain adequately described by 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 begins with 'Add a single contact' which clearly states the specific verb, resource, and scope (single vs. bulk). This distinguishes the tool from siblings like import_contacts (bulk import) and update_contact (modification).

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?

The description gives clear context on when to use the tool: only for adding contacts who have opted in, with an explicit warning about sender reputation and legal compliance. It does not explicitly name alternative tools like import_contacts for bulk operations, so alternatives are not stated, but the single-contact scope implies this.

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/Misar-AI/misarmail-mcp'

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