Skip to main content
Glama
Sign In

mailfloss

by com.mailfloss
OverviewDiscussionsAdmin

List verification jobs

list_jobs
Read-onlyIdempotent

Paginated history of verification jobs from every source, newest first (GET /v1/jobs). Free.

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_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque `pagination.next_cursor` from the previous page.
sourceNoHow the job was submitted. `api` = this REST API; `csv` = an in-app file upload; `input` = emails pasted into the in-app Copy & paste box; `widget` = the embeddable verification widget; `zapier` = the Zapier connector; `integration` = an ESP auto-cleanse (the ESP slug is in `source_integration`).
statusNoJob lifecycle state. queued = accepted, not yet processing; processing = in flight; completed = finished; cancelled = stopped before completion (by the customer, or by the system reaping a stalled job).
per_pageNoPage size, 1–100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond that: newest-first ordering, pagination behavior, all-source scope, the backing endpoint, and the fact that calls are free (no quota cost).

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?

One sentence, front-loaded with the resource and scope, parenthetically carrying the endpoint and cost. Zero filler.

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-required-param list tool with full schema coverage, no output schema and complete annotations, the description supplies the essential context: ordering, pagination, scope and cost. It stops short of saying what a job record contains or how deep the history goes, which would help an agent decide between this and the batch-specific getters.

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 both enums (source, status) are documented in detail in the schema itself. The description adds nothing about cursor, source, status or per_page, so 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?

Names a specific verb+resource (paginated history of verification jobs), the scope ('from every source'), ordering ('newest first') and the underlying endpoint. It is clear what it does, but it never contrasts itself with batch-oriented siblings like get_batch_status or get_batch_results, which an agent could easily confuse it with.

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?

'Paginated history ... from every source' implies this is the browse-all listing endpoint, and calling it free nudges toward exploratory use. There is no explicit statement of when to prefer it over get_batch_status/get_batch_results for a specific job, nor any exclusion.

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

All mailfloss toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources