Courier

track_inbound_event

Idempotent

Track an inbound event that can trigger automations. Requires event name, messageId (for deduplication), and properties.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event": "<event>",
      "messageId": "<messageId>",
      "properties": "<properties>"
    },
    "name": "track_inbound_event"
  }
}

Input Schema

Name	Required	Description
`event`	Yes	The event name (appears as trigger in Automation Trigger node)
`userId`	No	User ID associated with the event
`messageId`	Yes	Unique ID for deduplication (returns 409 if not unique)
`properties`	Yes	Event properties payload

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations by stating that tracking can trigger automations, which is a key side effect. It also highlights the deduplication role of messageId, complementing the idempotentHint annotation. No contradiction with annotations exists.

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 a single efficient sentence that front-loads the core purpose and then lists the required inputs. Every word earns its place; no filler or repetition of schema details.

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?

For a 4-parameter tool with a 100% covered schema and clear annotations, the description sufficiently covers what the tool does, what it requires, and its side effects. It does not describe response output, but no output schema exists and the core invocation context is complete.

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 description coverage is 100%, so the schema already documents all four parameters. The description restates the required parameters and adds little beyond the schema, aside from emphasizing messageId for deduplication, which the schema already mentions. 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 uses a specific verb ('Track') and resource ('inbound event') and states the purpose ('can trigger automations'). It clearly distinguishes this from sibling invoke_* tools by emphasizing inbound event ingestion rather than direct invocation.

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 phrase 'Track an inbound event' establishes clear context for external event ingestion, and 'that can trigger automations' signals its relationship to automation tools. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to select this over invoke_automation_template or invoke_ad_hoc_automation.

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

All Courier tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.