Skip to main content
Glama
GodisinHisHeaven

USCardForum MCP Server

bookmark_post

Save forum posts for later reference with optional labels, reminders, and auto-deletion settings. Requires user authentication to access USCardForum content.

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

  • MCP tool handler for bookmark_post. Decorated with @mcp.tool(). Includes input schema via Annotated Fields with descriptions. Executes by calling get_client().bookmark_post() with parameters and returns Bookmark.
    @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,
        )
  • Imports the bookmark_post tool from auth.py into the server_tools package, making it available for use and registration in the MCP server.
    from .auth import (
        login,
        get_current_session,
        get_notifications,
        bookmark_post,
        subscribe_topic,
    )
  • Imports bookmark_post tool in the main server entrypoint, ensuring it is registered with the MCP server upon startup.
    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,
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 by disclosing key behavioral traits: it states 'REQUIRES AUTHENTICATION' (security requirement), describes the return value ('Returns a Bookmark object'), and explains the default behavior for auto_delete_preference. However, it doesn't mention potential side effects like duplicate bookmarks, error conditions, or rate limits.

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 well-structured with purpose statement, authentication requirement, parameter explanations, prerequisite, return value, and usage context. While slightly verbose with some repetition of schema information, every section serves a purpose. The front-loaded purpose statement is clear and immediately actionable.

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

Completeness5/5

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

Given that this is a mutation tool with no annotations but with comprehensive schema coverage (100%) and an output schema (implied by 'Returns a Bookmark object'), the description provides complete context. It covers authentication requirements, parameter meanings, prerequisites, return values, and usage context - everything needed for an agent to correctly invoke this tool.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema: it repeats the post_id description verbatim and provides a slightly more detailed explanation of auto_delete_preference options. However, it doesn't add meaningful semantic context beyond what's already in the schema 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 the specific action ('Bookmark a post for later reference') and distinguishes it from all sibling tools, which are primarily get/read operations (e.g., get_topic_posts, get_user_summary). It explicitly identifies the resource being acted upon (a post) and the operation (bookmarking).

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?

The description provides explicit usage guidance: it states 'Must call login() first' as a prerequisite, and 'Use to save interesting posts for later reference' clarifies the intended context. While it doesn't explicitly mention when NOT to use it, the clear purpose and prerequisite make usage context unambiguous compared to read-only sibling tools.

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

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