Skip to main content
Glama
feuerdev
by feuerdev

list_note_collaborators

Retrieve the email addresses of all collaborators on a Google Keep note by providing the note ID.

Instructions

List collaborator emails for a note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'list_note_collaborators'. It retrieves a note by ID and returns a JSON array of collaborator email addresses from note.collaborators.all().
    @mcp.tool()
    def list_note_collaborators(note_id: str) -> str:
        """List collaborator emails for a note."""
        _, note = _get_note_or_raise(note_id)
        return json.dumps(list(note.collaborators.all()))
  • The tool is registered via the @mcp.tool() decorator, which registers 'list_note_collaborators' with the FastMCP server.
    @mcp.tool()
  • Helper function used by list_note_collaborators to retrieve a note by its ID. Returns (keep_client, note) or raises 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
  • The serialize_note function includes the collaborators list in its output payload, which is the same data source used by list_note_collaborators.
    'collaborators': list(note.collaborators.all()),
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It does not disclose behavioral traits like required permissions, response format, or whether it returns only emails. Minimal disclosure.

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 extremely concise, front-loaded, and contains no filler. However, it may be too brief, bordering on under-specification.

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 tool has one parameter, an output schema exists (but not described), and no annotations, the description is incomplete. It does not explain what the output contains or provide any usage context. With siblings, more details would help.

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?

The input schema has 0% description coverage, and the description adds no meaning beyond the schema. 'for a note' implies the note_id parameter, but no format or context is provided. The description does not compensate for the schema's lack of descriptions.

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 it lists collaborator emails for a note, using a specific verb and resource. It distinguishes from sibling tools like add_note_collaborator and remove_note_collaborator by implying a read operation.

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?

The description implies usage when needing to see collaborators, but provides no explicit guidance on when to use versus alternatives or any exclusions. It is adequate but lacks explicit direction.

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