Skip to main content
Glama

List print jobs

list_print_jobs
Read-only

Retrieve print jobs or orders newest first and filter results by status, date, search, or order ID with paging support.

Instructions

List Print-Jobs (orders), newest first by default, with optional filters and paging.

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

Input Schema

NameRequiredDescriptionDefault
idNoFilter by Print-Job id.
pageNoResult page, default 1.
searchNoSearch ids, external ids, order id, status, line item ids/titles/tracking ids and shipping address.
statusNoFilter by status: CREATED, REJECTED, UNPAID, PAYMENT_IN_PROGRESS, PRODUCTION_READY, PRODUCTION_DELAYED, IN_PRODUCTION, ERROR, SHIPPED or CANCELED.
order_idNoFilter by order id.
orderingNoField to sort by; prefix with '-' for descending.
page_sizeNoResults per page, default 100.
created_afterNoOnly items created after this ISO 8601 date or timestamp (UTC), e.g. '2026-11-09' or '2026-11-09T09:30:08Z'.
created_beforeNoOnly items created before this ISO 8601 date or timestamp (UTC), e.g. '2026-11-09' or '2026-11-09T09:30:08Z'.
modified_afterNoOnly items modified after this ISO 8601 date or timestamp (UTC), e.g. '2026-11-09' or '2026-11-09T09:30:08Z'.
modified_beforeNoOnly items modified before this ISO 8601 date or timestamp (UTC), e.g. '2026-11-09' or '2026-11-09T09:30:08Z'.
exclude_line_itemsNoLeave line items out of the response, for shorter results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds only the default sort order ('newest first by default'); it says nothing about result volume, whether line items are included by default (only the schema's exclude_line_items hints at it), or pagination metadata, so the added behavioral context is modest.

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

Conciseness4/5

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

A single front-loaded sentence with the resource and default ordering stated first and no filler. It is efficient, though the terseness leaves little room for the guidance an agent would benefit from.

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

Completeness3/5

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

For a 12-filter list tool with no output schema, the description says nothing about what a result record contains or whether line items appear by default, which matters for callers tuning response size. Annotations and the fully documented schema carry most of the burden, so the definition is workable but leaves a real gap around return shape.

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 all 12 filters documented in the schema including allowed status values and ISO 8601 date formats. The description adds no parameter meaning beyond that, which is acceptable given the schema does the work, but it earns no extra credit.

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 gives a specific verb and resource ('List Print-Jobs (orders)') plus the default ordering, which is enough to distinguish it from get_print_job and cancel_print_job by intent. It stops short of naming a sibling or stating scope boundaries explicitly, so it is clear but not maximally differentiating.

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?

'with optional filters and paging' implies the browsing/query use case, but there is no explicit when-to-use versus get_print_job (single job lookup) or get_print_job_statistics, and no stated conditions or preconditions. Usage is inferable from the name and phrase rather than spelled out.

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