Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_copy_image_object

Copies a native image from one Goodnotes document or page into another via Copy/Paste, checking source pixels and saved appearance while leaving the original intact.

Instructions

Copy one native image into another document/page through Goodnotes Copy/Paste. Requires sourceSha256 and region from image_crop_info; checks original pixels/crop and saved appearance. Source stays intact.

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": {
      "sourceUrl": "<sourceUrl>",
      "target": "<target>",
      "expectedSourceSha256": "<expectedSourceSha256>",
      "expectedCrop": "<expectedCrop>",
      "destinationPath": "<destinationPath>",
      "x": "<x>",
      "y": "<y>",
      "operationId": "<operationId>"
    },
    "name": "goodnotes_copy_image_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
targetYes
sourceUrlYes
operationIdYes
expectedCropYes
destinationPageNo
destinationPathYes
expectedSourceSha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=true. The description adds real behavior beyond that: it verifies original pixels, crop, and saved appearance, and 'Source stays intact' reassures the agent that the copy does not mutate the original. It still omits clipboard side effects inherent in a Copy/Paste path and whether the destination page must already exist.

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 short sentences, front-loaded with the action and followed by prerequisites and a safety note. No filler, though the fingerprint and crop constraints are packed densely enough to be slightly hard to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutation tool with nested objects and no output schema, this is thin. The agent is not told how to construct the target locator, whether destinationPage defaults matter, or what a success response proves, leaving major call-shaping decisions to guesswork.

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 9 parameters, so the description carries the full burden and mostly fails. It covers only the SHA-256 (called sourceSha256 versus the actual expectedSourceSha256), the crop region, and the destination document/page; the nested target object with its objectId/matchId/scanId resolution fields, destinationPath as a UUID breadcrumb, x/y placement, and operationId idempotency are all unexplained.

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 verb and resource: 'Copy one native image into another document/page'. The 'native image' qualifier implicitly separates it from goodnotes_copy_text_object and goodnotes_copy_page, though no sibling is named 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?

It points at a prerequisite workflow step by saying the sourceSha256 and region come from image_crop_info, which steers the agent to call that tool first. It gives no when-not guidance or explicit contrast with goodnotes_insert_image or goodnotes_copy_native_selection.

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