EmailOctopus MCP Server

List / segment contacts

list_contacts

Read-only

Retrieve contacts from an EmailOctopus list with filters for tag, status, and created or updated date ranges; returns paginated results up to 100 per page.

Instructions

List contacts in a list, filtered by tag, status, and created/updated date ranges (ISO 8601). Paginated, up to 100 per page.

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": {
      "listId": "<listId>"
    },
    "name": "list_contacts"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Only contacts with this tag
`limit`	No	Page size, 1-100
`listId`	Yes	List ID (from list_lists)
`status`	No
`created_after`	No
`updated_after`	No
`created_before`	No
`starting_after`	No	Cursor from a previous response's paging.next.starting_after
`updated_before`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 18, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior context — pagination with a 100-item cap and ISO 8601 date formats — but says nothing about auth requirements, rate limits, or how the cursor is used across calls.

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 tight sentences with zero filler; the core operation and its filter dimensions are front-loaded, and pagination follows immediately. Every clause carries information.

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 9-parameter read tool with no output schema and low schema coverage, the description is adequate but not complete: it never indicates the shape of the response (contacts plus paging cursors), which matters because there is no output schema to fall back on.

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 only 44% across 9 parameters, so the description must compensate. It does add the ISO 8601 format for the four date-range params (the schema leaves them bare) and the 1-100 page-size bound, but it is silent on the required listId, the starting_after cursor, and the status enum values.

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 (List) and resource (contacts) scoped to a list, and enumerates the filter dimensions (tag, status, date ranges). It is easily distinguished from single-contact siblings like get_contact, though it never names an alternative explicitly.

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?

Usage is implied by the phrasing 'List contacts in a list, filtered by...' but there is no explicit when-to-use guidance, no statement of when to prefer get_contact/upsert_contact, and no preconditions. An agent can infer the intent but gets no routing help.

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

Deploy Server