Skip to main content
Glama
Sign In

Sending

by dev.sending
OverviewDiscussionsAdmin

List UTM touches

list_utm_touches
Read-only

Lists the workspace UTM touches (email clicks, site events, PostHog) with filters and pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_utm_touches"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO date: window end
fromNoISO date: window start
pageNo
sourceNoemail_click | event | stripe | posthog
campaignNoExact utm_campaign
pageSizeNo
contactIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / campaign / description
      Previous value: -"utm_campaign esatta"New value: +"Exact utm_campaign"
    • changedInput schema / properties / from / description
      Previous value: -"ISO date: inizio finestra"New value: +"ISO date: window start"
    • changedInput schema / properties / to / description
      Previous value: -"ISO date: fine finestra"New value: +"ISO date: window end"
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context on what a 'touch' is (email clicks, site events, PostHog) and notes pagination, but says nothing about rate limits, default window, or result ordering beyond the annotation.

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?

A single, front-loaded sentence that names the resource before its details. It wastes nothing, though it is arguably too terse to give the agent the guidance it needs.

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?

For a 7-param, read-only list tool with no output schema, the description is minimally adequate: it explains what is listed and that filtering/pagination exist. It omits differentiation from list_utm_conversions and does not cover the half of parameters left undocumented in the schema.

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

Parameters2/5

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

Schema coverage is only 57%, so the description should help fill gaps, yet it adds nothing beyond the generic phrase 'filters and pagination'. It never explains the meaning or format of source, campaign, or the date window beyond what the schema already shows.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Lists') and resource ('workspace UTM touches') and even enumerates the touch sources (email clicks, site events, PostHog). It is clear what the tool returns, though it never distinguishes 'touches' from the sibling list_utm_conversions or get_utm_summary.

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?

The description gives no when-to-use guidance and no exclusions. With closely related siblings like list_utm_conversions and get_utm_summary in scope, the agent is left to infer which tool to pick, and 'with filters and pagination' is a capability statement, not usage guidance.

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

All Sending toolsInspect
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.

Resources