Skip to main content
Glama
Sign In

Milanote MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Invite editor

invite_editor
Destructive

Invite someone by email to edit a board and the boards inside it. Adds the address as an editor, as Share, Invite editors via email does, and Milanote emails them a link. status is invited when they have no Milanote account yet (a free one is enough to edit), active when they do. Milanote allows inviting only once your account's email is verified; the free plan limits how many boards you can share. Remove them in the Share dialog to undo it. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.

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": {
      "board_id": "<board_id>",
      "email": "<email>"
    },
    "name": "invite_editor"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesTheir email address.
board_idYesBoard ID from list_boards, or the board URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that Milanote emails the invitee a link, that status depends on whether they already have an account, that email verification and plan limits apply, and that calls wait for owner approval. It also explains that confirmation is on by default but can be switched off, which is valuable behavioral context for a destructive sharing mutation.

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?

The description is front-loaded with the core purpose and then proceeds through relevant caveats in a logical order. It is somewhat verbose, especially the reference to the Share dialog and the confirmation default, but most sentences carry useful context.

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

Completeness5/5

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

For an open-world, destructive, non-idempotent sharing mutation with no output schema, the description covers prerequisites, status semantics, limits, undo behavior, confirmation, and approval waiting. That is enough for an agent to understand the call's full operational context.

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 description coverage is 100%, so the schema already documents both email and board_id. The description does not add format or sourcing details beyond the schema's existing guidance, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: inviting someone by email to edit a board and its nested boards. It distinguishes the action from the Share dialog flow and implicitly from remove_editor by describing the inverse operation.

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?

It gives clear prerequisites (email verification, plan sharing limits) and status outcomes (invited vs active) that tell the agent when the call will behave as expected. It also mentions undoing via the Share dialog, but it does not explicitly route the agent to the sibling remove_editor tool for revocation.

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

All Milanote MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources