Skip to main content
Glama
Sign In
EmailOctopus MCP Server

EmailOctopus MCP Server

by OfirOhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get list

get_list
Read-only

Retrieve one EmailOctopus mailing list, including its custom fields and tags, by list ID.

Instructions

Get one list, including its custom fields and tags.

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

Input Schema

NameRequiredDescriptionDefault
listIdYesList ID (from list_lists)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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, covering the safety profile. The description adds that the response includes custom fields and tags, which is useful return-context, but does not disclose any further behavior such as auth requirements or rate limits.

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?

A single, front-loaded sentence with no wasted words. The essential operation and its included data are stated immediately.

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 simple read-only getter with one fully documented parameter and no output schema, the description adequately covers the operation and what content is returned. It could be slightly more complete by mentioning how the ID is obtained, but the schema already handles that.

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%, and the single listId parameter is fully documented in the schema (including its source from list_lists). The description adds no extra parameter meaning, so the baseline 3 applies.

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 (Get) and resource (one list), and notes the included sub-resources (custom fields and tags). It distinguishes itself from list_lists by specifying 'one list', but does not explicitly name the sibling it is not.

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 when-to-use guidance or alternatives are given. The description implies retrieving a single list by ID but does not state when this is preferable to list_lists or other list-related siblings.

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

Deploy Server

Other Tools