Skip to main content
Glama
RyoJerryYu

MCP Server Memos

by RyoJerryYu

list_memo_tags

List memo tags by specifying the parent memo (or 'memos/-' for all) and visibility level. Filter tags to find those owned by a specific memo or with public, protected, or private visibility.

Instructions

List all existing memo tags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentNoThe parent, who owns the tags. Format: memos/{id}. Use "memos/-" to list all tags. memos/-
visibilityNoThe visibility of the tags.PRIVATE

Implementation Reference

  • The async handler function that executes the 'list_memo_tags' tool logic. Validates input using ListMemoTagsRequest, constructs a gRPC request, calls memo_service.list_memo_tags(), and returns tag names as text content.
    async def list_memo_tags(self, args: dict) -> list[types.TextContent]:
        try:
            params = ListMemoTagsRequest.model_validate(args)
        except Exception as e:
            raise McpError(types.INVALID_PARAMS, str(e))
    
        req = memos_api_v1.ListMemoTagsRequest(
            parent=params.parent,
            filter=f"visibilities == ['{params.visibility.value}']",
        )
        res = await self.memo_service.list_memo_tags(list_memo_tags_request=req)
        content = ", ".join(res.tag_amounts.keys())
        content = f"Tags:\n{content}"
        return [types.TextContent(type="text", text=content)]
  • Pydantic model for the tool input schema (parent and visibility fields). Used for validation and as the JSON schema for the tool registration.
    class ListMemoTagsRequest(BaseModel):
        """Request to list memo tags"""
    
        parent: Annotated[
            str,
            Field(
                default="memos/-",
                description="""The parent, who owns the tags.
    Format: memos/{id}. Use "memos/-" to list all tags.
    """,
            ),
        ]
        visibility: Annotated[
            Visibility,
            Field(default=Visibility.PRIVATE, description="""The visibility of the tags."""),
        ]
  • Enum definition registering 'list_memo_tags' as a tool name in MemosTools.
    class MemosTools(str, Enum):
        LIST_MEMO_TAGS = "list_memo_tags"
  • Tool registration in list_tools() function, providing description and inputSchema for the tool.
    types.Tool(
        name=MemosTools.LIST_MEMO_TAGS,
        description="List all existing memo tags",
        inputSchema=ListMemoTagsRequest.model_json_schema(),
    ),
  • Call routing in call_tool() that dispatches to the list_memo_tags handler when the tool name matches.
    elif name == MemosTools.LIST_MEMO_TAGS:
        return await tool_adapter.list_memo_tags(args)
Behavior2/5

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

No annotations provided; description does not disclose read-only nature, rate limits, or whether listing all tags includes inherited visibility. The tool is likely safe but unstated.

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

Conciseness5/5

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

Efficient single sentence, front-loaded with purpose, no unnecessary words.

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?

No output schema and description does not clarify return structure, but the tool is simple and siblings do not provide tags, so minimal completeness suffices.

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 coverage is 100% with descriptions for both parameters; description adds no additional meaning beyond 'list all tags'.

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?

Description clearly states verb 'list' and resource 'memo tags', but omits that filtering is available via parameters, making it slightly incomplete.

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 siblings like get_memo or search_memo, nor any prerequisites or exclusions.

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/RyoJerryYu/mcp-server-memos-py'

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