Skip to main content
Glama

human_list_tasks

List dispatched human tasks with optional filters by status, backend, or category, and pagination. Results sorted newest first.

Instructions

List all dispatched human tasks with optional filters and pagination.

Returns tasks sorted by creation time (newest first). Use filters to narrow results by status, backend, or category.

PARAMETERS:

  • status: (optional) Filter by task status: pending, routed, completed, failed, cancelled

  • backend_id: (optional) Filter by backend: webhook_provider, manual

  • category: (optional) Filter by category: errand, photo_video, data_collection, verification, delivery, digital_micro, in_person, custom

  • limit: (optional) Max results to return, 1-100, default 20

  • offset: (optional) Skip N results for pagination, default 0

RETURNS: { total, count, tasks[], has_more, next_offset }

EXAMPLES:

  1. List all tasks: {}

  2. List completed tasks: { status: "completed" }

  3. List webhook provider tasks: { backend_id: "webhook_provider", limit: 10 }

  4. Paginate: { limit: 5, offset: 5 }

DON'T USE WHEN:

  • You know the exact task_id (use human_get_task_status for a single task)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of tasks to return (1-100, default 20)
offsetNoNumber of tasks to skip for pagination (default 0)
statusNoFilter tasks by status (e.g. 'pending', 'completed')
categoryNoFilter tasks by their category
backend_idNoFilter tasks by which backend is handling them
Behavior5/5

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

No annotations provided, so description fully discloses behavior: tasks sorted by creation time (newest first), pagination details, and return structure. No contradictions.

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?

Well-structured with clear sections (purpose, sorting, parameters, returns, examples, don't use). Front-loaded with essential info, no wasted words.

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, it describes returns. All 5 parameters fully documented, no annotations needed. Complete for a listing tool.

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%, but description adds defaults, enum values, and use cases through examples, going beyond schema descriptions.

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 all dispatched human tasks with optional filters and pagination. It distinguishes from sibling tools like human_get_task_status, which is for a single task.

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?

Explicitly says 'DON'T USE WHEN' and directs to human_get_task_status for a single task. Provides examples for various filters and pagination, but could mention when to use other siblings like human_list_backends.

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/zyntarasystems/human-dispatch-mcp'

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