Skip to main content
Glama

Add page numbers to a PDF

add_page_numbers
Idempotent

Number the pages of your PDFs: at the bottom or top, on one side or in the centre, and from the page and number you choose. Returns a link to download the result (kept about an hour). Credits on paid plans: 5 per file.

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": {
      "files": "<files>"
    },
    "name": "add_page_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage. Language of the texts the tool adds. Values: 'es' = Spanish; 'en' = Englishes
filesYesInput files (.pdf). Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).
firstNoStart numbering on page
startNoFirst number
formatNoFormat Values: 'n' = 1, 2, 3…; 'n-de-t' = 1 / 10; 'pagina' = Page 1 of 10n
positionNoPosition Values: 'abajo-centro' = Bottom centre; 'abajo-derecha' = Bottom right; 'abajo-izquierda' = Bottom left; 'arriba-centro' = Top centre; 'arriba-derecha' = Top right; 'arriba-izquierda' = Top leftabajo-centro

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, open-world behavior, so the bar is lower, and the description still adds two facts the agent cannot get elsewhere: the result is a download link that expires in about an hour, and the operation costs 5 credits per file on paid plans. It does not mention what happens to the original file, but for a non-destructive transform that is minor.

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 sentences, zero waste: the capability and its options come first, followed by the two operational facts an agent actually needs (return link lifetime, credit cost). Nothing is repeated from the schema or annotations.

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

Completeness4/5

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

With no output schema, the description usefully states that the return value is a download link with a roughly one-hour lifetime, and it discloses cost. Parameter behavior is fully covered by the rich schema, so the only unaddressed item is error/partial-failure behavior when multiple files are supplied.

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%, so the schema already documents every parameter, including the enum values and defaults. The description only paraphrases the position and numbering options already spelled out in the schema and adds no format strings, constraints, or interaction rules, 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?

"Number the pages of your PDFs" is a specific verb+resource, and the follow-up clauses state the configurable axes (top/bottom, side/centre, start page, first number). No sibling tool covers page numbering, so no disambiguation is needed; the only gap is that the purpose is stated in marketing tone ("your PDFs") rather than operational terms.

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?

Usage is implied by the single-purpose nature of the tool and by the enumerated positioning choices, but there is no explicit when-to-use or when-not-to-use statement, and no mention of prerequisites such as input files needing to be PDFs (that only appears in the schema). Adequate but with clear gaps.

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