sparkpost-mcp

search_message_events

Search and filter message events by time range, event types, recipients, and domains. Paginate results with cursor and per_page for efficient browsing.

Instructions

Search message events (one page; cursor + per_page for paging)

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": "search_message_events"
  }
}

Input Schema

Name	Required	Description
`to`	No	End of time range (ISO-8601)
`from`	No	Start of time range (ISO-8601)
`cursor`	No	Pagination cursor from previous response links
`events`	No	Filter by event types
`per_page`	No	Results per page (1–10000)
`recipients`	No	Comma-delimited recipient emails
`recipient_domains`	No	Comma-delimited recipient domains

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist. The description mentions pagination behavior but omits details on safety (e.g., read-only nature), authorization needs, or rate limits. It is adequate but not thorough.

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 a single efficient sentence with key pagination info. No wasted words, though slightly more structure could be beneficial.

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?

Given 7 parameters and no output schema, the description provides minimal behavioral context (pagination). Lacks details on return format, common use cases, or prerequisites, making it only minimally 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 parameters. The description adds no new information about parameters, resulting in baseline score.

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 ('Search') and resource ('message events'), and adds pagination context ('one page; cursor + per_page for paging'). It effectively distinguishes from sibling tools, which are largely different in nature.

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 implies usage for searching events with pagination but does not provide explicit when-to-use or when-not-to-use guidance, nor alternatives like get_deliverability_metrics.

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