Skip to main content
Glama
Sign In

Mailjet MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get campaign report in Mailjet

mailjet_get_campaign_report
Read-onlyIdempotent

Get campaign report in the user's own Mailjet account from ChatGPT, Claude or any AI agent. Returns how to do it in Mailjet step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Mailjet Cloud Browser. Mailjet's official API: Mailjet has a full REST API (v3) for contacts, segments, campaign drafts, scheduling, sending and statistics, and an official MCP server that is read-only: it does not send emails or change Mailjet settings (checked 22 Oct 2026).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: it produces a step-by-step guide with screens, buttons, and fields, and explicitly does not open or change anything by itself. It also notes that Mailjet's official MCP server is read-only, reinforcing safe usage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and next step are front-loaded, but the final sentence about Mailjet's full REST API and official read-only MCP server is tangential and dated. It adds length without helping an agent decide or invoke this specific tool more accurately.

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 zero-parameter, read-only guidance tool with no output schema and clear annotations, the definition provides enough context to call it correctly. The only shortfall is that the extra API/MCP sentence is not needed for completeness and slightly dilutes focus.

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

Parameters4/5

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

The tool has zero parameters, so there is no parameter semantics to explain; baseline is 4 for this dimension. The description correctly does not invent parameters or imply configuration options.

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?

The description states a specific verb and resource ("Get campaign report in the user's own Mailjet account") and clarifies that it returns step-by-step instructions rather than opening anything itself. It distinguishes itself from the browser tools by explicitly saying it "opens nothing by itself" and directs subsequent action to cotlet_browser_* tools.

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?

It gives clear usage context: first retrieve this guide, then perform the task using the cotlet_browser_* tools in the Mailjet Cloud Browser. It does not explicitly state when not to use it or name a competing sibling, but the intended workflow is unambiguous.

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

All Mailjet MCP Server and API by Cotlet 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