Remove PDF Pages — Remove specific pages from a PDF document. Runs in the browser. Covered by signup welcome credits and by the Day Pass (24-hour unlimited on this workspace group). All three credit-based workspaces unlock with the same one-time credit pack — there is no per-workspace subscription. See mioffice.ai/pricing for current plans.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but only discloses that it runs in the browser. It does not explain whether the original file is modified, how the output is delivered, whether the operation is reversible, or any restrictions. The extensive credit/pricing information is not behavioral.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description front-loads the core purpose in the first sentence, but then diverts into lengthy credit and pricing details that are not directly relevant to tool invocation. It is not excessively long, but the pricing sentences add noise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite the absence of a schema, the description gives no indication of how the input PDF or page numbers are supplied, what the tool returns, or any prerequisites. It only states purpose and billing, leaving the agent without enough context to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, so the baseline is 4. The description does not need to explain parameters, but it also does not clarify how page selection or file input is provided, which would be useful. However, with 0 params, the baseline applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description begins with 'Remove specific pages from a PDF document,' clearly stating the tool's function with a specific verb and resource. It distinguishes itself from sibling PDF tools like split, merge, and compress by focusing on page removal.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives such as mio_pdf_split or mio_pdf_editor. It only mentions the browser-run environment and credit coverage, not scenarios where this tool is preferred or excluded.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools have overlapping purposes, such as mio_ai_remove_background and mio_ai_remove_background_pro, mio_ai_video_subtitler and mio_video_auto_captions, and mio_ai_enhancer tools targeting similar media. Agents would struggle to pick the correct tool when several appear to do nearly the same thing.
Naming conventions are mixed: most tools use a mio_ prefix with category, but some use action-based names (mio_image_compress), others use format-pair names (mio_image_avif_to_jpg), and a few use a different prefix (mioffice_list_tools, mioffice_pricing_info). The lack of a uniform pattern makes the tool set harder to navigate.
With 134 tools, the server is massively over-scoped. Even for a broad workspace suite, this count exceeds practical limits and creates significant selection overhead for agents. The number is more appropriate for a full product catalog than an MCP tool surface.
The tool set covers a wide range of PDF, image, audio, video, scanner, and AI operations, so most common tasks are represented. However, there are notable gaps for a 'workspace studio,' such as no document creation or spreadsheet editing tools, and the redundancy between overlapping AI tools suggests the surface is not thoughtfully curated.
