Skip to main content
Glama

Удалить страницы

delete_pages

Удаляет указанные страницы из PDF. file_url: публичный URL PDF-файла. pages: список номеров страниц для удаления (1-based).

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": {
      "file_url": "<file_url>",
      "pages": "<pages>"
    },
    "name": "delete_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYes
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, and the description's 'публичный URL' reinforces the open-world fetch requirement. What it omits is the consequence: whether the original file is modified or a new PDF is returned, whether the operation is reversible, and how it fails. Note a tension worth flagging: destructiveHint=false sits uneasily with a page-deletion tool, though this is likely an annotation mislabel rather than a description error, since a new output file is presumably produced (an output schema exists).

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?

Three short lines: the action first, then one line per parameter. Nothing is repeated from the schema, no filler, and the reading order matches the order an agent needs to reason about the call.

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 an output schema present, return values need not be described, and both required parameters are explained. Still missing for a two-parameter mutation tool: the fate of the source file, behavior on invalid or exhaustive page lists, and any size constraints on the public URL. Adequate but with visible gaps.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does: file_url is defined as a public URL to the PDF, and pages as a list of page numbers, explicitly 1-based — the single most error-prone detail for this call. It stops short of covering edge cases such as out-of-range indices, duplicates, ordering, or whether a page count limit 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?

The first sentence states a specific verb and resource: 'Удаляет указанные страницы из PDF' (deletes the specified pages from a PDF). An agent can immediately distinguish this from conversion siblings such as pdf_to_word or compress_pdf. However, it never contrasts itself with the closest neighbours, extract_pages, split_pdf and reorder_pages, which operate on page selection and could be mistaken for it.

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 only implied by the purpose: if you need pages removed, call this. There is no statement of when to prefer split_pdf or extract_pages instead, no note that the source must be a publicly reachable PDF rather than a local upload, and no guidance on maximum page count or invalid ranges. The context is clear enough for a well-known operation, but the agent gets no explicit routing rules.

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.