Skip to main content
Glama

PDF Page Numbers API - add page numbers to a PDF

pdf_page_numbers
Read-onlyIdempotent

Stamp page numbers on every page: position (6 places), style (1 / Page 1 / Page 1 of N / - 1 -), first number, text size, optional no number on the cover page. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/pdf-page-numbers.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "format": "of",
      "fileName": "sample.pdf",
      "fileContent": "JVBERi0xLjMKJeLjz9MKMSAwIG9iago8PAovUHJvZHVjZXIgKHB5cGRmKQo+PgplbmRvYmoKMiAwIG9iago8PAovVHlwZSAvUGFnZXMKL0NvdW50IDEKL0tpZHMgWyA0IDAgUiBdCj4+CmVuZG9iagozIDAgb2JqCjw8Ci9UeXBlIC9DYXRhbG9nCi9QYWdlcyAyIDAgUgo+PgplbmRvYmoKNCAwIG9iago8PAovVHlwZSAvUGFnZQovUmVzb3VyY2VzIDw8Cj4+Ci9NZWRpYUJveCBbIDAuMCAwLjAgNTk1IDg0MiBdCi9QYXJlbnQgMiAwIFIKPj4KZW5kb2JqCnhyZWYKMCA1CjAwMDAwMDAwMDAgNjU1MzUgZiAKMDAwMDAwMDAxNSAwMDAwMCBuIAowMDAwMDAwMDU0IDAwMDAwIG4gCjAwMDAwMDAxMTMgMDAwMDAgbiAKMDAwMDAwMDE2MiAwMDAwMCBuIAp0cmFpbGVyCjw8Ci9TaXplIDUKL1Jvb3QgMyAwIFIKL0luZm8gMSAwIFIKPj4Kc3RhcnR4cmVmCjI1NgolJUVPRgo="
    },
    "name": "pdf_page_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoText size in points, default 10
filesNoOr several files: [{fileName, fileContent (base64)}]
startNoFirst page number, default 1
formatNon = 1, page = Page 1, of = Page 1 of N, dash = - 1 -n
fileNameNoFile name with extension, e.g. report.pdf
positionNobc bottom center, br, bl, tc top center, tr, tlbc
skipFirstNoNo number on the first page (cover)
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / size / minimum
      Added value: +0
    • addedInput schema / properties / start / minimum
      Added value: +0
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Well beyond the readOnly/openWorld/idempotent annotations, it discloses that processing happens server-side, that files are deleted immediately with nothing stored, a concrete free-tier limit (25 calls/day per IP), and paid pricing ($0.005/call via x402 with a URL). Privacy, rate-limit, and cost traits are exactly the context an agent needs before calling.

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?

Two dense sentences, capability first and operational constraints second, with no filler. Slightly compressed into one long sentence block, but every clause carries information.

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?

With 8 optional parameters and no output schema, the definition never explains what comes back — returned PDF as base64, a link, or nothing — nor how the single-file parameters interact with the `files` array. Annotations and the parameter prose cover input and safety, but a key output-side gap remains.

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% and the enums already document position codes and format styles, so the schema does the heavy lifting. The description's restatement of positions, styles, first number, size, and cover skip adds readable reinforcement but no syntax or edge-case meaning beyond the schema, so baseline 3 applies.

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?

"Stamp page numbers on every page" is a specific verb plus resource, and the enumerated options (position, style variants like "Page 1 of N", starting number, cover-page skip) make the operation unmistakable. It does not explicitly name a sibling such as pdf_watermark to delineate itself, so it falls short of the top mark.

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?

The description implies when this applies (you have a PDF and want numbering, with options for cover pages), but gives no explicit when-to-use/when-not guidance and does not route to alternatives like pdf_watermark or pdf_organize. The reader must infer the selection context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources