Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_insert_image

Inserts a local PNG or JPEG into an allowed Goodnotes document, uploads it, verifies appearance after reload, and returns a selection for moving or resizing.

Instructions

Insert an explicitly supplied local PNG/JPEG into an allowed document and verify its appearance after reload. Uploads this image to Goodnotes. Returns a selection for moving/resizing.

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": {
      "viewId": "<viewId>",
      "filePath": "<filePath>",
      "operationId": "<operationId>"
    },
    "name": "goodnotes_insert_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewIdYes
filePathYes
operationIdYes

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 the safety profile (not read-only, open-world, non-destructive); the description adds real behavioral detail beyond them: the image is uploaded to Goodnotes, appearance is verified after reload, and the call yields a selection handle for move/resize. It does not disclose failure behavior for disallowed file types or documents, which keeps it from a 5.

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?

Three compact sentences, front-loaded with the action and input constraint, followed by side effect and return value. 'Uploads this image to Goodnotes' is slightly redundant with 'insert ... into an allowed document' but still adds the upload step, so waste is minimal.

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 mutation tool with three required, fully undocumented parameters and no output schema, the definition explains the visible behavior and return value but leaves the caller unable to fill in viewId or operationId correctly. It is adequate on behavior and incomplete on invocation.

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 description coverage is 0% across three required parameters, so the description must carry the load, yet it names none of them. 'FilePath' is loosely implied by 'local PNG/JPEG' but the UUID viewId and especially the operationId (likely an idempotency key given its pattern) receive no explanation at all.

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 description states a specific verb and resource (insert a local PNG/JPEG into a document) plus an outcome (a selection for moving/resizing). 'Explicitly supplied local' implicitly separates it from object-copying siblings like goodnotes_copy_image_object, but no sibling is named, so differentiation is inferred rather than stated.

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 'allowed document' and 'explicitly supplied' hint at preconditions (permitted target document, caller-provided file rather than an existing page object), but there is no explicit when-to-use, when-not-to-use, or named alternative such as copy/crop object tools. Usage is implied rather than guided.

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