Skip to main content
Glama

Reprint (re-order) books

reprint_print_job

Place a new Lulu book order by reusing printable_ids from an earlier Print-Job, so files don't need to be sent again. Applies the same payment rules as creating a job.

Instructions

Place a new order for books Lulu already has, using each line item's printable_id from an earlier Print-Job, so files don't need to be sent again. Same payment rules as create_print_job.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contact_email": "<contact_email>",
      "shipping_level": "<shipping_level>",
      "shipping_address": "<shipping_address>",
      "line_items": "<line_items>"
    },
    "name": "reprint_print_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
line_itemsYes
external_idNoYour own order number or reference.
contact_emailYesEmail Lulu uses for questions about this Print-Job.
shipping_levelYesShipping service level, from slowest/cheapest (MAIL) to fastest (EXPRESS).
production_delayNoMinutes (60 to 2880) to wait before production starts, leaving time to cancel.
shipping_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false. The description usefully adds that no files are re-sent and that payment rules mirror create_print_job, signaling this is a real, billable order. However, it never warns that repeated calls create duplicate orders — the single most important behavioral fact given idempotentHint=false — and says nothing about what the response contains.

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?

Two tight sentences with the core action and the key benefit (no re-upload) front-loaded, followed by the payment caveat. Nothing is redundant.

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 6-parameter, nested-object mutation tool with no output schema, the definition covers the essential what and why but omits the return value (presumably a new print job id) and duplicate-order risk. An agent could call it correctly but would be under-informed about consequences and follow-up steps.

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 a solid 67%, and the schema already explains printable_id, pod_package_id, shipping_level and production_delay in detail. The description only reinforces printable_id's origin ('from an earlier Print-Job'), adding little beyond the structured fields and leaving shipping/production_delay tradeoffs untouched. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Place a new order for books Lulu already has') and immediately differentiates itself from the sibling creation tool by explaining that files 'don't need to be sent again'. An agent can tell this is the re-order path rather than a fresh upload.

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?

The description makes the selection condition clear: use this when the books already exist at Lulu and you hold printable_ids, otherwise you need the file-uploading path. It names create_print_job as the reference point for payment behavior but does not state explicit exclusions or prerequisites (e.g. the prior job must have succeeded).

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