Skip to main content
Glama
resend

Email Sending MCP

by resend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Contact Import

create-contact-import

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.

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. Prefer content or url on a remote server, where filePath is disabled by default. 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.
filePathNoPath to a CSV file on the machine that runs this MCP server. The server can restrict or disable local file reads. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.26.1
    • changedInput schema / properties / filePath / description
      Previous value: -"Local path to a CSV file to read and upload. Use one of filePath, content, or url."New value: +"Path to a CSV file on the machine that runs this MCP server. The server can restrict or disable local file reads. Use one of filePath, content, or url."
  2. Changed1 schema field changedv2.12.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv2.10.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description does the heavy lifting: it discloses asynchronous processing, that an import ID is returned immediately, the 100MB size cap, and that filePath may be disabled server-side. It omits auth/permission requirements and rate limits, but the key operational behaviors are covered.

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?

Front-loaded with purpose, then the async workflow, then parameter selection guidance, then limit. Every sentence carries actionable content; no filler.

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 an async, 8-parameter tool with no output schema, the description covers input sourcing, exactly-one constraint, environment caveats, size limit, and the polling follow-up. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds real value beyond the schema by stating the parameters are mutually exclusive ('exactly one of') and the environment-dependent behavior of filePath, plus the size limit.

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?

Specific verb (bulk-import) + resource (contacts) + method (from a CSV file), and it names the streaming follow-up tool get-contact-import. An agent can distinguish it from create-contact (single) and list-contact-imports without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: call this, then use get-contact-import to poll status/counts. It also states the selection rule among filePath/content/url and the environment condition (prefer content/url where filePath is disabled), leaving nothing to inference.

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

Deploy Server

Other Tools