Skip to main content
Glama
rhettlong

USCardForum MCP Server

by rhettlong

bookmark_post

Save posts from USCardForum for later reference with optional labels, reminders, and auto-delete settings. Requires authentication.

Instructions

Bookmark a post for later reference. REQUIRES AUTHENTICATION.

Args:
    post_id: The numeric post ID to bookmark
    name: Optional label/name for the bookmark
    reminder_type: Optional reminder setting
    reminder_at: Optional reminder datetime (ISO format)
    auto_delete_preference: When to auto-delete (default: 3)
        - 0: Never
        - 1: When reminder sent
        - 2: On click
        - 3: Clear after 3 days

Must call login() first.

Returns a Bookmark object with the created bookmark information.

Use to save interesting posts for later reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYesThe numeric post ID to bookmark
nameNoLabel/name for the bookmark
reminder_typeNoReminder setting
reminder_atNoReminder datetime (ISO format)
auto_delete_preferenceNoWhen to auto-delete: 0=never, 1=when reminder sent, 2=on click, 3=after 3 days (default)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesBookmark ID
nameNoBookmark label
reminder_atNoReminder time
bookmarkable_idYesBookmarked item ID
bookmarkable_typeNoType of bookmarked itemPost
auto_delete_preferenceNoAuto-delete setting

Implementation Reference

  • The MCP tool handler for 'bookmark_post', decorated with @mcp.tool(). Defines input parameters with Pydantic Field descriptions for schema validation. Delegates to the client implementation and returns a Bookmark object.
    @mcp.tool()
    def bookmark_post(
        post_id: Annotated[
            int,
            Field(description="The numeric post ID to bookmark"),
        ],
        name: Annotated[
            str | None,
            Field(default=None, description="Label/name for the bookmark"),
        ] = None,
        reminder_type: Annotated[
            int | None,
            Field(default=None, description="Reminder setting"),
        ] = None,
        reminder_at: Annotated[
            str | None,
            Field(default=None, description="Reminder datetime (ISO format)"),
        ] = None,
        auto_delete_preference: Annotated[
            int | None,
            Field(
                default=3,
                description="When to auto-delete: 0=never, 1=when reminder sent, 2=on click, 3=after 3 days (default)",
            ),
        ] = 3,
    ) -> Bookmark:
        """
        Bookmark a post for later reference. REQUIRES AUTHENTICATION.
    
        Args:
            post_id: The numeric post ID to bookmark
            name: Optional label/name for the bookmark
            reminder_type: Optional reminder setting
            reminder_at: Optional reminder datetime (ISO format)
            auto_delete_preference: When to auto-delete (default: 3)
                - 0: Never
                - 1: When reminder sent
                - 2: On click
                - 3: Clear after 3 days
    
        Must call login() first.
    
        Returns a Bookmark object with the created bookmark information.
    
        Use to save interesting posts for later reference.
        """
        return get_client().bookmark_post(
            post_id,
            name=name,
            reminder_type=reminder_type,
            reminder_at=reminder_at,
            auto_delete_preference=auto_delete_preference,
        )
  • Pydantic BaseModel defining the Bookmark output schema returned by the bookmark_post tool, including fields like id, bookmarkable_id, name, reminder_at, and auto_delete_preference.
    class Bookmark(BaseModel):
        """A bookmarked post."""
    
        id: int = Field(..., description="Bookmark ID")
        bookmarkable_id: int = Field(..., description="Bookmarked item ID")
        bookmarkable_type: str = Field("Post", description="Type of bookmarked item")
        name: str | None = Field(None, description="Bookmark label")
        reminder_at: datetime | None = Field(None, description="Reminder time")
        auto_delete_preference: int = Field(3, description="Auto-delete setting")
    
        class Config:
            extra = "ignore"
  • Main server entrypoint imports all server_tools including bookmark_post from uscardforum.server_tools, which triggers registration of the @mcp.tool() decorated functions.
    from uscardforum.server_tools import (
        analyze_user,
        bookmark_post,
        compare_cards,
        find_data_points,
        get_all_topic_posts,
        get_categories,
        get_current_session,
        get_hot_topics,
        get_new_topics,
        get_notifications,
        get_top_topics,
        get_topic_info,
        get_topic_posts,
        get_user_actions,
        get_user_badges,
        get_user_followers,
        get_user_following,
        get_user_reactions,
        get_user_replies,
        get_user_summary,
        get_user_topics,
        list_users_with_badge,
        login,
        research_topic,
        resource_categories,
        resource_hot_topics,
        resource_new_topics,
        search_forum,
        subscribe_topic,
    )
  • Re-exports bookmark_post from .auth submodule, making it available for import in server.py.
    from .auth import (
        login,
        get_current_session,
        get_notifications,
        bookmark_post,
        subscribe_topic,
    )
Behavior4/5

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

With no annotations provided, the description carries full burden and does well: it discloses authentication requirement ('REQUIRES AUTHENTICATION'), mentions the return type ('Returns a Bookmark object'), and describes auto-delete behavior with default values. It doesn't cover rate limits or error conditions, but provides substantial operational context.

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?

Well-structured with purpose statement, authentication warning, parameter details, prerequisite, return value, and usage context. The auto_delete_preference explanation is somewhat lengthy but informative. Overall efficient with minimal redundancy.

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

Completeness4/5

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

For a mutation tool with no annotations but an output schema, the description provides good coverage: clear purpose, authentication requirement, parameter guidance, return type mention, and usage context. It could mention potential errors or idempotency, but covers the essential operational aspects adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the auto_delete_preference enum values in detail (0-3 with meanings) and clarifying that name, reminder_type, and reminder_at are optional. It doesn't add syntax details beyond schema, but the enum explanation is helpful.

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 verb ('bookmark') and resource ('a post'), specifying it's for 'later reference'. It distinguishes from sibling tools like 'get_topic_posts' or 'get_user_actions' by focusing on saving rather than retrieving content.

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

Usage Guidelines5/5

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

Explicitly states 'Must call login() first' for authentication prerequisites and 'Use to save interesting posts for later reference' for context. It doesn't mention alternatives, but the authentication requirement and purpose provide clear usage boundaries.

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/rhettlong/uscardforum-mcp'

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