Skip to main content
Glama
Davison-Francis

@deliveriq/mcp

List Verification Jobs

deliveriq_list_jobs
Read-onlyIdempotent

List batch email verification jobs with pagination and status filters to track pending, processing, completed, failed, or cancelled jobs. View job IDs, statuses, email counts, and dates.

Instructions

List batch verification jobs with pagination and optional status filter.

Args:

  • page (number): Page number (default: 1)

  • limit (number): Results per page (default: 20, max: 100)

  • status (string, optional): Filter by "pending", "processing", "completed", "failed", or "cancelled"

Returns: Table of jobs with ID, status, email count, and dates.

Credit cost: Free

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1)
limitNoResults per page (default: 20, max: 100)
statusNoFilter by job status

Implementation Reference

  • The async handler function for deliveriq_list_jobs. Calls client.batch.list() with page/limit/status params, formats results as a Markdown table with job IDs, statuses, email counts, and pagination info.
      async (params) => {
        try {
          const res = await client.batch.list({
            page: params.page,
            limit: params.limit,
            status: params.status,
          });
    
          if (res.jobs.length === 0) {
            return successResponse('No verification jobs found.' + (params.status ? ` (filter: ${params.status})` : ''));
          }
    
          const lines = [
            `# Verification Jobs`,
            '',
            `Page ${res.pagination.page} of ${res.pagination.totalPages} (${res.pagination.total} total)`,
            '',
            '| Job ID | Status | Emails | Created |',
            '|--------|--------|--------|---------|',
          ];
    
          for (const job of res.jobs) {
            lines.push(`| ${job.id} | ${job.status} | ${job.processedEmails}/${job.totalEmails} | ${job.createdAt} |`);
          }
    
          if (res.pagination.page < res.pagination.totalPages) {
            lines.push('', `*Use page: ${res.pagination.page + 1} to see more results.*`);
          }
    
          return successResponse(lines.join('\n'));
        } catch (error) {
          return handleSdkError(error);
        }
      },
    );
  • Input schema (Zod) for deliveriq_list_jobs: page (int, min 1, default 1), limit (int, 1-100, default 20), optional status enum (pending/processing/completed/failed/cancelled).
    export const ListJobsSchema = z.object({
      page: z.number().int().min(1).default(1)
        .describe('Page number (default: 1)'),
      limit: z.number().int().min(1).max(100).default(20)
        .describe('Results per page (default: 20, max: 100)'),
      status: z.enum(['pending', 'processing', 'completed', 'failed', 'cancelled']).optional()
        .describe('Filter by job status'),
    }).strict();
  • Registration of the tool named 'deliveriq_list_jobs' on the McpServer with title 'List Verification Jobs', description, inputSchema, annotations (readOnly, idempotent), and handler via server.registerTool().
      server.registerTool(
        'deliveriq_list_jobs',
        {
          title: 'List Verification Jobs',
          description: `List batch verification jobs with pagination and optional status filter.
    
    Args:
      - page (number): Page number (default: 1)
      - limit (number): Results per page (default: 20, max: 100)
      - status (string, optional): Filter by "pending", "processing", "completed", "failed", or "cancelled"
    
    Returns:
      Table of jobs with ID, status, email count, and dates.
    
    Credit cost: Free`,
          inputSchema: ListJobsSchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: true,
          },
        },
        async (params) => {
          try {
            const res = await client.batch.list({
              page: params.page,
              limit: params.limit,
              status: params.status,
            });
    
            if (res.jobs.length === 0) {
              return successResponse('No verification jobs found.' + (params.status ? ` (filter: ${params.status})` : ''));
            }
    
            const lines = [
              `# Verification Jobs`,
              '',
              `Page ${res.pagination.page} of ${res.pagination.totalPages} (${res.pagination.total} total)`,
              '',
              '| Job ID | Status | Emails | Created |',
              '|--------|--------|--------|---------|',
            ];
    
            for (const job of res.jobs) {
              lines.push(`| ${job.id} | ${job.status} | ${job.processedEmails}/${job.totalEmails} | ${job.createdAt} |`);
            }
    
            if (res.pagination.page < res.pagination.totalPages) {
              lines.push('', `*Use page: ${res.pagination.page + 1} to see more results.*`);
            }
    
            return successResponse(lines.join('\n'));
          } catch (error) {
            return handleSdkError(error);
          }
        },
      );
  • Credit cost constant: deliveriq_list_jobs costs 0 credits (free).
    deliveriq_list_jobs: 0,
  • The successResponse helper used by the handler to format successful results.
    export function successResponse(text: string): McpContent {
      return { content: [{ type: 'text', text: truncateResponse(text) }] };
    }
Behavior4/5

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

Annotations already indicate readOnly, idempotent, and not destructive. The description adds that it returns a table with specific fields and states the credit cost is free, providing useful behavioral context beyond annotations.

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 concise and well-structured: main purpose first, then parameter details in Args format, and return statement. No extraneous information.

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 no output schema, the description explains the return format (fields included). It covers pagination, filter options, and credit cost, making it complete for the tool's complexity.

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?

Schema coverage is 100% with all parameters documented, but the description adds meaning by specifying the return format and that page defaults to 1, limit defaults to 20 with max 100, which reinforces the schema.

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 it lists batch verification jobs with pagination and status filter, distinguishing it from sibling tools like deliveriq_batch_download and deliveriq_check_credits.

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 explains when to use the tool (listing jobs with pagination and status filter) but does not explicitly mention when not to use it or alternative tools. However, the context of sibling tools makes the usage clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Davison-Francis/min8t-sdks'

If you have feedback or need assistance with the MCP directory API, please join our Discord server