Skip to main content
Glama
feuerdev
by feuerdev

list_note_media

Get a list of media blobs and direct links from a Google Keep note using its note ID.

Instructions

List note media blobs and direct media links when available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool handler function 'list_note_media' decorated with @mcp.tool(). It retrieves a note by ID, iterates over its blobs, collects blob_id, type, and media_link, then returns JSON.
    @mcp.tool()
    def list_note_media(note_id: str) -> str:
        """List note media blobs and direct media links when available."""
        keep, note = _get_note_or_raise(note_id)
    
        media = []
        for blob in note.blobs:
            media.append(
                {
                    "blob_id": blob.id,
                    "type": blob.blob.type.value if blob.blob and blob.blob.type else None,
                    "media_link": keep.getMediaLink(blob),
                }
            )
    
        return json.dumps(media)
  • Helper function '_get_note_or_raise' used by list_note_media to fetch a note by ID or raise a 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 @mcp.tool() decorator registers 'list_note_media' as an MCP tool with the FastMCP server.
    @mcp.tool()
  • Type signature: input parameter 'note_id: str', return type 'str' (JSON serialized list).
    def list_note_media(note_id: str) -> str:
Behavior2/5

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

No annotations exist, so the description must carry the burden. It only implies a read operation ('list') but does not disclose details like pagination, rate limits, or behavior when media is unavailable. The phrase 'when available' hints at conditional output but is too vague.

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 a single, front-loaded sentence with no waste. It efficiently states the core function, though it could be slightly more structured with separate notes for usage.

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

Completeness3/5

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

With a simple one-parameter input and an output schema (presumably), the description minimally covers the necessary context. However, it lacks details like return format or error handling, which are partially mitigated by the output schema's existence.

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 description coverage is 0%, so the description should add meaning to parameters. It does not explain the purpose or format of note_id beyond what the name implies. No additional context is provided for the sole parameter.

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 tool lists 'note media blobs and direct media links when available,' specifying the verb (list) and resource (note media). It distinguishes from sibling tools like get_note or list_labels by focusing on media assets.

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 usage guidelines are provided. The description does not indicate when to use this tool over others (e.g., get_note for full note content). No context about prerequisites or alternatives is given.

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