Skip to main content
Glama
feuerdev
by feuerdev

add_note_collaborator

Add a collaborator email to a Google Keep note using the note ID and email address.

Instructions

Add a collaborator email to a note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes
emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool handler for add_note_collaborator. It gets the note via _get_note_or_raise, ensures modifiability, adds the collaborator email, syncs, and returns the serialized note.
    @mcp.tool()
    def add_note_collaborator(note_id: str, email: str) -> str:
        """Add a collaborator email to a note."""
        keep, note = _get_note_or_raise(note_id)
        _ensure_modifiable(note)
    
        note.collaborators.add(email)
        keep.sync()
        return json.dumps(serialize_note(note))
  • Registration via the @mcp.tool() decorator on the add_note_collaborator function. The function name is the tool name.
    @mcp.tool()
    def add_note_collaborator(note_id: str, email: str) -> str:
  • Input schema is defined implicitly by the function signature: note_id (str) and email (str).
    def add_note_collaborator(note_id: str, email: str) -> str:
  • _get_note_or_raise helper used by the handler to retrieve the note or raise ValueError.
    def _get_note_or_raise(note_id: str):
        keep = get_client()
        note = keep.get(note_id)
        if not note:
            raise ValueError(f"Note with ID {note_id} not found")
        return keep, note
  • _ensure_modifiable helper used by the handler to check if the note can be modified.
    def _ensure_modifiable(note):
        if not can_modify_note(note):
            raise ValueError(
                f"Note with ID {note.id} cannot be modified "
                "(missing keep-mcp label and UNSAFE_MODE is not enabled)"
            )
Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It only says 'Add', implying mutation, but provides no details on idempotency, error conditions, or side effects like notifications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence) and front-loaded, but it sacrifices necessary detail. It is efficient but not sufficiently informative.

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?

Given the absence of annotations and the presence of an output schema, the description still lacks important context such as error handling, duplicate behavior, and permissions, making it incomplete for an agent.

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%, and the description adds minimal semantics beyond parameter names. It does not explain the format of email or the nature of note_id (e.g., whether it's a UUID or title).

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 clearly states the action 'Add' and the resource 'collaborator email to a note', distinguishing it from siblings like remove_note_collaborator. However, it lacks explicit differentiation from other note-related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as list_note_collaborators or remove_note_collaborator. Missing context about prerequisites or conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/feuerdev/keep-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server