Skip to main content
Glama
resend

Email Sending MCP

by resend

Create Contact Import

create-contact-import

Import contacts from a CSV file into Resend. Provide the CSV via file path, raw content, or URL. Works asynchronously, returning an import ID to track progress.

Instructions

Bulk-import contacts from a CSV file into Resend. The import is processed asynchronously: this returns an import ID immediately, then use get-contact-import to poll its status and counts. Provide the CSV via exactly one of filePath, content, or url. Max file size 100MB.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL of a CSV file to fetch and upload. Use one of filePath, content, or url.
topicsNoTopic subscription configurations applied to the imported contacts.
contentNoRaw CSV text to upload (e.g. "email,first_name\na@b.com,Ada"). Use one of filePath, content, or url.
filePathNoLocal path to a CSV file to read and upload. Use one of filePath, content, or url.
filenameNoName for the uploaded file. Defaults to "contacts.csv".
columnMapNoMaps contact fields to CSV header names. When omitted, headers are matched case-sensitively to "email", "first_name", and "last_name".
onConflictNoHow to handle contacts that already exist: "upsert" updates them, "skip" leaves them unchanged. Defaults to "upsert".
segmentIdsNoArray of segment IDs to assign the imported contacts to.
Behavior4/5

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

No annotations are provided, so the description fully covers behavioral aspects: async processing, immediate return of import ID, max file size 100MB, and the requirement to use exactly one of three CSV sources. It lacks details on error handling or validation behaviors.

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 extremely concise, with two sentences that front-load the core purpose and key usage details. Every sentence contributes meaningful information without redundancy.

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?

The description covers the main points but lacks explanation of the return format (no output schema) and details about CSV structure beyond the schema. For a complex import tool with 8 parameters, more guidance on expected CSV format and column mapping would improve completeness.

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%, but the description adds value by clarifying the mutual exclusivity of 'filePath', 'content', and 'url', and specifying the 100MB file size limit, which are not in the schema description.

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 verb 'bulk-import' and resource 'contacts', with a specific, unique action. It distinguishes from the sibling tool 'create-contact' by focusing on CSV file import and asynchronous processing.

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 explicitly mentions the asynchronous nature and directs to 'get-contact-import' for polling, providing clear context. However, it does not explicitly state when not to use this tool (e.g., for single contacts) relative to siblings like 'create-contact'.

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/resend/resend-mcp'

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