Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_prepare_study_collection

Copy a lecture and export a stable source snapshot for multiple automatically sized learning boards, reusing verified study preparation and a stable request ID to prevent duplicate copies.

Instructions

Copy a lecture and export a stable source snapshot for multiple automatically sized learning boards. Reuses the verified study preparation; a stable requestId prevents duplicate copies.

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": {
      "sourceItemPath": "<sourceItemPath>",
      "expectedSourceTitle": "<expectedSourceTitle>",
      "title": "<title>",
      "requestId": "<requestId>"
    },
    "name": "goodnotes_prepare_study_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
requestIdYes
folderPathNo
sourceItemPathYes
expectedSourceTitleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare write, non-destructive, open-world; the description adds genuinely new behavior: it creates multiple boards, exports a stable snapshot, and requestId provides idempotency against duplicate copies. It does not cover failure/partial-result behavior or permission requirements.

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, front-loaded with the verb and resource, and the idempotency note earns its place. 'Automatically sized learning boards' is slightly vague but not wasteful.

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?

For a 5-parameter write tool with no output schema and no per-parameter documentation, the description conveys the high-level operation and idempotency but leaves parameter meaning and result shape underspecified.

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

Parameters2/5

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

Schema coverage is 0% across five parameters; only requestId is explained (duplicate prevention). sourceItemPath, expectedSourceTitle, title and folderPath remain unexplained, and expectedSourceTitle in particular looks like a verification guard that an agent must understand.

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 a specific compound action: copy a lecture, export a snapshot, and produce multiple learning boards. The 'study collection' scope distinguishes it from the board/revision siblings, though it never names an alternative explicitly.

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 phrase 'reuses the verified study preparation' implies this is downstream of a prior planning step, but no sibling is named and there is no explicit when-to-use or when-not guidance versus plan/review/run collection tools.

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