Skip to main content
Glama
kanjidoc
by kanjidoc

missive_create_message

Creates a simulated inbound message in a Missive custom channel to import or test message workflows without external delivery.

Instructions

ADVANCED — custom channels only. Creates an INCOMING message record (a simulated inbound message) inside a Missive custom channel; it NEVER transmits anything externally and is NOT an email send. To actually send an email, use the Drafts endpoint with send (not exposed by this server). from_field is required; account (the custom-channel account ID) falls back to MISSIVE_DEFAULT_ACCOUNT.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoMessage body — HTML or plain text depending on the channel message type.
teamNoTeam ID to link the conversation to (ignored if the conversation already has a team).
closeNoClose the message's conversation for everyone with access.
accountNoCustom-channel account ID (found in the custom channel settings). Falls back to MISSIVE_DEFAULT_ACCOUNT.
subjectNoEmail-channel only: message subject.
add_usersNoUser IDs to grant access to the conversation. Requires `organization`.
cc_fieldsNoEmail-channel only: CC recipients ([{ address, name }]).
to_fieldsNoRecipients. Email channel: [{ address, name }]. Text/HTML channel: [{ id, username, name }].
bcc_fieldsNoEmail-channel only: BCC recipients ([{ address, name }]).
force_teamNoForce a new team even if the conversation is already in another team.
from_fieldYesRequired. The message sender. Email channel: { address, name }. Text/HTML channel: { id, username, name }.
referencesNoReference strings used to append this message to an existing conversation (matched against prior external_id/references). If none match, a new conversation is created.
attachmentsNoFiles to attach. Total request payload must not exceed 10 MB.
external_idNoUnique ID identifying non-email messages (SMS, Instagram DMs, etc.).
add_to_inboxNoMove the conversation to Inbox for everyone with access.
conversationNoID of an existing conversation to append this message to (alternative to references).
delivered_atNoDelivery timestamp (Unix seconds). If omitted, delivered-at is set to request time.
organizationNoOrganization ID. Scopes the conversation search and links a newly created conversation. REQUIRED when using add_users / add_assignees / remove_assignees.
add_assigneesNoUser IDs to assign to the conversation (existing assignees remain). Requires `organization`.
remove_assigneesNoUser IDs to unassign from the conversation. Requires `organization`.
add_shared_labelsNoShared-label IDs to apply to the message's conversation.
add_to_team_inboxNoMove the conversation to a team inbox. Requires `team`.
conversation_colorNoConversation color: a HEX code (e.g. "#000") or one of "good" / "warning" / "danger".
conversation_subjectNoSubject to set on the conversation.
remove_shared_labelsNoShared-label IDs to remove from the message's conversation.
Behavior4/5

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

The description adds transparency beyond the annotation (destructiveHint=false) by explaining that the tool creates a simulated inbound message, never transmits externally, and is not an email send. It also notes the fallback behavior for the 'account' parameter.

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?

The description is concise, conveying essential information in three sentences. It avoids unnecessary fluff, though could be slightly more structured by separating the warning from the usage notes.

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 complexity (25 parameters, no output schema), the description covers the core purpose, usage constraints, and key parameter details. It does not describe the return value, but the schema and context signals compensate. Overall, it provides sufficient context for 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?

While the input schema already covers all 25 parameters with descriptions (100% coverage), the description adds extra context for key parameters like 'from_field' (required) and 'account' (fallback to default), and clarifies channel-type variations for message fields.

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 it creates an INCOMING message record in a Missive custom channel, and explicitly distinguishes it from sending an email. It names the alternative endpoint (Drafts) and specifies it never transmits externally.

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?

The description starts with 'ADVANCED — custom channels only', providing immediate usage context. It explicitly says when to use (custom channels) and when not to (not for email sending), and directs to the correct alternative for sending emails.

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/kanjidoc/missive-mcp'

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