Skip to main content
Glama

machfive

by io.github.Bluecraft-AI

List Lead Lists

list_lists
Read-onlyIdempotent

List lead lists (batch jobs) in the user's MachFive workspace.

Useful for browsing past batches, checking what's in progress, or finding a list_id to export. Results are ordered newest first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return, 1-100.
offsetNoPagination offset.
statusNoFilter by processing status: 'pending', 'processing', 'completed', or 'failed'.
campaign_idNoFilter by campaign UUID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds useful behavioral context beyond annotations by noting results are ordered newest first and explaining typical use cases. This goes beyond simple annotation repetition.

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?

The description is two sentences, front-loaded with the core purpose and followed by concrete use cases. Every sentence earns its place with no wasted words, making it highly concise and well structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (handling return values) and fully documented parameters, the description covers purpose, usage context, and an important behavioral trait (ordering). It is complete for a simple read-only list tool and aligns well with sibling tools.

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%, with each parameter already well-described in the input schema. The description itself does not add parameter-level detail, so it meets the baseline for high schema coverage without needing to compensate.

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 tool lists lead lists (batch jobs) in the user's workspace, using specific verb+resource. It distinguishes from sibling tools like list_campaigns (which lists campaigns) and get_list_status (single status) by focusing on the collection of lead lists.

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 provides clear context on when to use the tool: for browsing past batches, checking progress, or finding a list_id to export. It does not explicitly name alternatives or exclusions, but the use cases imply when it's appropriate, which earns a 4 rather than a 5.

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

All machfive toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a distinct purpose: list_campaigns provides campaign IDs, generate_batch and generate_sequence handle async batch and sync single generation respectively, get_list_status polls progress, export_list retrieves completed results, and list_lists browses past batches. The descriptions clearly differentiate the overlapping generate tools with explicit usage guidance.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., list_campaigns, generate_batch, export_list). The verbs are clear and the nouns accurately reflect the resources/actions, making the API predictable.

Tool Count5/5

With 6 tools, the server is well-scoped for its purpose of generating and managing email sequences. Each tool serves a necessary role in the workflow, and the count is ideal—not overwhelming, not sparse.

Completeness5/5

The tool set covers the full lifecycle: discover campaigns, submit batch or single-lead generation, poll status, retrieve results, and browse past batches. There are no obvious missing operations that would prevent an agent from completing the core workflow.

Resources