Skip to main content
Glama

loops

by io.usefulapi

Send an event

loops_send_event
Destructive

Sends an event to Loops for a contact — TRIGGERS any automations/loops subscribed to this event. Loops API: POST /v1/events/send.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoContact email (supply email or userId).
userIdNoContact userId (supply email or userId).
eventNameYesThe event name to send (required).
mailingListsNoMap of mailing-list id -> subscribed boolean.
eventPropertiesNoProperties attached to this event.
contactPropertiesNoContact properties to update alongside the event.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Discloses that sending an event triggers automations, which goes beyond annotations. No contradictions with destructiveHint: true.

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 with no fluff. Front-loads the action and side effect.

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?

Covers main purpose and side effect, but no details on return values, error behaviors, or additional context for the 6 parameters.

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%, so description adds no extra parameter meaning beyond what the schema already provides.

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?

Clearly states it sends an event and triggers automations. Distinguishes from sibling tools like loops_create_contact or loops_delete_contact.

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

Usage Guidelines2/5

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

No guidance on when to use vs alternatives, no exclusion criteria or prerequisites mentioned.

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

All loops toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool has a distinct purpose and target resource (contacts, properties, lists, events, transactional emails, API key). No overlap or ambiguity in descriptions.

Naming Consistency5/5

All tools follow a consistent 'loops_verb_noun' pattern in snake_case. Verbs are descriptive and nouns match the resource.

Tool Count5/5

10 tools is well-scoped for the domain, covering contacts, properties, lists, events, transactional emails, and an API test. Neither sparse nor overloaded.

Completeness4/5

Covers core contact CRUD, property creation, listing, and sending capabilities. Minor gap: no update/delete for contact properties, but the surface handles primary workflows.

Resources