Skip to main content
Glama
feuerdev
by feuerdev

remove_note_collaborator

Remove a collaborator email from a Google Keep note. Provide the note ID and the collaborator's email to revoke access.

Instructions

Remove a collaborator email from a note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes
emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the remove_note_collaborator tool. It fetches the note by ID, ensures it can be modified, removes the collaborator email from the note, syncs with Google Keep, and returns the updated note as JSON.
    @mcp.tool()
    def remove_note_collaborator(note_id: str, email: str) -> str:
        """Remove a collaborator email from a note."""
        keep, note = _get_note_or_raise(note_id)
        _ensure_modifiable(note)
    
        note.collaborators.remove(email)
        keep.sync()
        return json.dumps(serialize_note(note))
  • The tool is registered using the @mcp.tool() decorator from FastMCP, which registers it as an MCP tool named 'remove_note_collaborator'.
    @mcp.tool()
    def remove_note_collaborator(note_id: str, email: str) -> str:
  • Helper function that retrieves a note by ID or raises an error if not found. Used by remove_note_collaborator.
    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
  • Helper function that checks if a note can be modified before performing operations like removing a collaborator.
    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)"
            )
  • Helper function that serializes a note (including its collaborators list) to a dictionary for JSON output.
    def serialize_note(note):
        """
        Serialize a Google Keep note into a dictionary.
        
        Args:
            note: A Google Keep note object
            
        Returns:
            dict: A dictionary containing the note's id, title, text, pinned status, color and labels
        """
        payload = {
            'id': note.id,
            'title': note.title,
            'text': note.text,
            'type': note.type.value,
            'pinned': note.pinned,
            'archived': note.archived,
            'trashed': note.trashed,
            'color': note.color.value if note.color else None,
            'labels': [serialize_label(label) for label in note.labels.all()],
            'collaborators': list(note.collaborators.all()),
        }
    
        if hasattr(note, 'items'):
            payload['items'] = [serialize_list_item(item) for item in note.items]
    
        payload['media'] = [
            {
                'blob_id': blob.id,
                'type': blob.blob.type.value if blob.blob and blob.blob.type else None,
            }
            for blob in note.blobs
        ]
    
        return payload
Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It only says 'Remove' implying mutation, but no details on side effects, reversibility, or error handling are given.

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 a single sentence with no wasted words, but it is too sparse to be fully informative, scoring average.

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 no annotations and no parameter descriptions, the description is incomplete. An output schema exists but is not referenced, and return values or error behavior are not explained.

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?

With 0% schema description coverage, the description adds no extra meaning to the two parameters beyond their names. It mentions 'collaborator email' but does not clarify format or validation.

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 clearly states the action (remove) and the resource (collaborator email from a note), distinguishing it from siblings like add_note_collaborator and list_note_collaborators.

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 is provided on when to use this tool vs alternatives, nor any prerequisites such as the note existence or collaborator association.

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