Skip to main content
Glama
spruikco

send16-mcp

by spruikco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

send_event

Fire a custom event to trigger automations for a contact. Include a payload to pass data to automation conditions.

Instructions

Fire a custom event for a contact. Automations whose trigger is {type:'custom_event', eventName:'<name>'} will enroll the contact and start running. Payload is exposed to condition steps as event.<key>.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesEvent name (e.g. 'trial_started', 'order.placed')
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
payloadNoArbitrary JSON metadata available to automation conditions
contactIdNoContact UUID (provide either this or contactEmail)
occurredAtNoISO-8601 timestamp; defaults to now
contactEmailNoContact email (provide either this or contactId)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.7

TDQS

A4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that automations trigger, payload is exposed to conditions, and mentions event name pattern. It does not cover rate limits or idempotency, but core behavior is clear.

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?

Two sentences, front-loaded with core action, no redundancy. Every sentence provides value.

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 6 parameters, nested payload, and no output schema, the description explains the automation enrollment effect and payload exposure. Missing details on response/return value but sufficient for the tool's primary purpose.

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

Parameters3/5

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

Schema coverage is 100% with all parameters described inline. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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 action ('fire a custom event for a contact'), the resource (contact), and the trigger effect (automations with matching event name enroll the contact). It distinguishes from siblings like 'enroll_in_automation' by explaining it's event-driven.

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

Usage Guidelines3/5

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

The description explains the consequence (automation enrollment) but does not explicitly state when to use this tool vs alternatives (e.g., 'enroll_in_automation'). Usage is implied but not contrasted.

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