get_user_actions
Fetch a user's activity feed with optional filtering by action type for detailed analysis of likes, topics, replies, and mentions.
Instructions
Fetch a user's activity feed with optional filtering.
Args:
username: The user's handle
filter: Action type filter (optional). Common values:
- 1: Likes given
- 2: Likes received
- 4: Topics created
- 5: Replies posted
- 6: Posts (all)
- 7: Mentions
offset: Pagination offset (0, 30, 60, ...)
Returns a list of UserAction objects showing what the user has done.
Use this for detailed activity analysis beyond just replies.
For most cases, get_user_replies or get_user_topics are simpler.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | The user's handle | |
| filter | No | Action type filter: 1=likes given, 2=likes received, 4=topics created, 5=replies posted, 6=all posts, 7=mentions | |
| offset | No | Pagination offset (0, 30, 60, ...) |
Implementation Reference
- The main handler function for the 'get_user_actions' MCP tool. It defines the input schema using Annotated types and Pydantic Field, executes the logic by calling the client API, and specifies the return type as list[UserAction]. This is the core implementation of the tool.@mcp.tool() def get_user_actions( username: Annotated[ str, Field(description="The user's handle"), ], filter: Annotated[ int | None, Field( default=None, description="Action type filter: 1=likes given, 2=likes received, 4=topics created, 5=replies posted, 6=all posts, 7=mentions", ), ] = None, offset: Annotated[ int | None, Field(default=None, description="Pagination offset (0, 30, 60, ...)"), ] = None, ) -> list[UserAction]: """ Fetch a user's activity feed with optional filtering. Args: username: The user's handle filter: Action type filter (optional). Common values: - 1: Likes given - 2: Likes received - 4: Topics created - 5: Replies posted - 6: Posts (all) - 7: Mentions offset: Pagination offset (0, 30, 60, ...) Returns a list of UserAction objects showing what the user has done. Use this for detailed activity analysis beyond just replies. For most cases, get_user_replies or get_user_topics are simpler. """ return get_client().get_user_actions(username, filter=filter, offset=offset)
- src/uscardforum/server_tools/__init__.py:37-47 (registration)Registration via import in the server_tools package __init__.py, exposing get_user_actions as part of the public tools API.from .users import ( get_user_summary, get_user_topics, get_user_replies, get_user_actions, get_user_badges, get_user_following, get_user_followers, get_user_reactions, list_users_with_badge, )
- src/uscardforum/server.py:15-45 (registration)Top-level registration in the main server.py file, importing all tools including get_user_actions for exposure to the MCP server.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, )
- Imports the UserAction model used as the return type for get_user_actions, defining the output schema.FollowList, UserAction, UserBadges, UserReactions, UserSummary, )
- src/uscardforum/server_tools/users.py:303-313 (registration)Explicit export of get_user_actions in users.py __all__, making it available for import.__all__ = [ "get_user_summary", "get_user_topics", "get_user_replies", "get_user_actions", "get_user_badges", "get_user_following", "get_user_followers", "get_user_reactions", "list_users_with_badge", ]