Cloudlabels

List PDFs

list_pdfs

Read-onlyIdempotent

Requires items.read. List stored PDFs for this organization. Reading the list does not delete old files. Returns id, filename, size, and created_at. Use get_print_job with the PDF id to get a download link. source or type is included only when the stored file already has one. page starts at 1. page_size is 10 to 100, same as list_items. The pagination object matches list_items: page, pageSize, totalItems, totalPages, hasNextPage, hasPreviousPage. Includes used and limit when this plan has a PDF cap.

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

Input Schema

Name	Required	Description	Default
`page`	No
`page_size`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description still adds meaningful context: reading does not delete old files, source/type appear only when already stored, and the response includes plan cap fields (used/limit). That is more than the annotations could convey.

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?

Front-loaded with the permission and core purpose, then return fields, then paging. Dense but every sentence carries information; the tone is slightly list-like but no filler is present.

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?

No output schema exists, yet the description documents return fields, conditional fields (source/type), pagination object members, and plan-cap extras — everything an agent needs to interpret a call's result without extra sources.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no per-parameter descriptions), so the description must carry the load — it states page starts at 1 and page_size is 10–100, matching and explaining the schema bounds, and notes both mirror list_items semantics. The paging object shape is also spelled out field by field.

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 ('List stored PDFs for this organization') and scopes it to the organization, which distinguishes it from single-file tools like get_print_job. The return fields are enumerated so the agent knows exactly what comes back.

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?

Gives a clear next-step route ('Use get_print_job with the PDF id to get a download link') and states the required permission (items.read). It doesn't say when not to use it, but no sibling list tool competes for this resource.

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

All Cloudlabels tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?