Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_combine_pdf

Combine selected pages from local PDF exports into a new PDF in your chosen order, without changing cloud originals. Import the resulting file separately if needed.

Instructions

Combine or extract selected pages from existing local PDF exports into a new local PDF, preserving supplied order. Never modifies cloud originals. Import the resulting path explicitly if desired.

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": {
      "parts": "<parts>"
    },
    "name": "goodnotes_combine_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsYes
titleNoCombined notes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already signal a non-read-only but non-destructive operation; the description reinforces this by guaranteeing cloud originals are never modified and that a brand-new local file is produced, which is exactly the mutation-scope context an agent needs. It also discloses that page order is preserved and that the output is a path requiring an explicit import step, rather than describing a return payload.

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 sentences, front-loaded with the core action, followed by the safety guarantee and then the next-step hint. No filler or repetition.

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?

For a two-parameter tool with no output schema, the description covers what is produced (a new local PDF at a path), that originals are untouched, and what to do with the result. The main omission is that the title parameter and per-export page addressing rules are left entirely undocumented.

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 coverage is 0%, so the description carries the burden, and it partially does: "selected pages from existing local PDF exports" maps to the parts/exportId/pages structure and "preserving supplied order" explains ordering semantics of the array. However, it says nothing about the title parameter, page-number indexing base, or the 50-part cap, so real gaps remain.

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?

States specific verbs ("combine or extract") and a precise resource ("selected pages from existing local PDF exports") plus the output ("a new local PDF"). It implicitly separates itself from goodnotes_import_pdf by telling the agent to import the result afterwards, though it never names the sibling explicitly.

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?

"Combine or extract selected pages from existing local PDF exports" establishes the precondition that source material must already be a local export, and the closing sentence tells the agent what to do next (import the returned path if needed). It stops short of naming alternatives such as an export tool for producing those inputs.

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

Deploy Server

Other Tools