MCP reference
Browse the generated MCP tool reference.
The input pages use mcpInputSchema when a capability supplies one, matching the schema advertised to MCP clients. JSON Schema describes the transport shape; OAuth authorization, refinements, and runtime business rules still apply.
Sheet content management
Section titled “Sheet content management”Use edit_sheet_content after get_sheet, passing the exact updated_at as expectedUpdatedAt and the same organization. The tool accepts 1–200 sequential add, remove, move, and set_score edits in one atomic request. Removing a member leaves the exercise intact. Scores affect only this sheet and do not enable scoring mode.
add optionally takes beforeExerciseId (omitted/null appends) and scorePoints (omitted means unset for a new member). move requires beforeExerciseId; null moves to the end. set_score requires a nullable score: zero is valid, null clears, and values from 0 to 99999.9 allow one decimal place. Anchors must exist at that edit’s position in the sequence. Use source IDs in subsequent edits even when private reuse will create a copy. The applied result maps those sources to actual IDs. Removing and reinserting an original member preserves identity and its omitted score.
Set dryRun: true to inspect proposed rows, required copies and publication confirmation without resource changes or successful-write audit records. Preview still requires write authority. A public destination may return canApply: false and a make_exercises_public requirement; explicitly set confirmMakeExercisesPublic: true only after reviewing that consequence. Preview does not reserve source state; apply checks it again.
Applied results include complete ordered rows, exact before/after revisions, copy mappings, publication IDs, a sheet link and a versioned write receipt. A final no-op preserves the revision/version. Invalid or stale edits have no partial resource effects; indexed errors identify the offending edit. The complete result has a 1 MiB limit.
After an uncertain response, inspect get_sheet and version history before preparing another edit. Do not blindly resend. Readback cannot prove attribution or reconstruct an unacknowledged copy mapping; this tool does not provide replayable idempotency. Existing append and metadata-update tools remain available.