Sort

AgentEarth Tool Catalog

Social Media

852Tools
12tags
14Providers

Query social media profiles, posts, notes, comments and interaction data for account research, topic tracking and content performance analysis across platforms such as X (Twitter), RedNote (Xiaohongshu), Reddit and TikTok.

  1. Find information using accounts, content URLs or keywords, and retrieve followers, likes, comments and other data through the relevant tools.
  2. Support brand monitoring, competitor account research, topic tracking and content performance analysis with data for agent research tasks.

Tool List

852 tools

ae_x_check_user_live_status

Check whether an X (Twitter) user is currently live. Input: `rest_id` is required and must be the user's numeric ID supplied as a string, for example `"44196397"`. Do not supply a username or screen name. Result: Returns data describing the user's current live status. Specific result fields and status values are not documented. If a screen name is supplied, the response contains placeholder data with all fields set to `"s"`; this is not a valid live-status result.

ae_x_get_community_members

Retrieve the first page of members of an X (Twitter) community. Inputs: - community_id (required string): The community ID, for example "1493290339532222469". - cursor (optional string): Omit this parameter. Pagination is currently unsupported; it cannot be used to retrieve more members. Returns: A community member list limited to the first page, approximately 19 members. This is not a complete membership list. A next_cursor may appear in the response, but passing it back returns an empty list rather than another page. This tool is unsuitable for retrieving all community members.

ae_x_get_community_timeline

Retrieve posts from an X community timeline. Inputs: - community_id (required string): The community ID, for example "1493290339532222469". - ranking (optional string): Relevance or Recency. Omit this input to use the default ordering. - cursor (optional string): The pagination cursor from the previous response. Omit it for the initial request. Returns: A page of the community's posts in the response data. Use the returned cursor, when available, to request the next page. Detailed post fields are not specified by this tool's response schema. Example: {"community_id":"1493290339532222469","ranking":"Recency"}

ae_x_get_list_followers

Retrieve followers of an X (Twitter) List. Inputs: - list_id (required string): The List ID, for example "84839422". - cursor (optional string): Omit for the initial request. To request another page, use next_cursor from the previous response when available. Returns: A response containing follower data for the specified List. Detailed follower record fields are not specified. These are accounts following the List, not the List's members or the followers of an individual account. Example: {"list_id":"84839422"}

ae_x_search_communities

Search X (Twitter) communities using a keyword. Inputs: - keyword (required string): The search term, for example "superman". - cursor (optional string): A pagination cursor. Omit it for the first page; for subsequent pages, use next_cursor from the previous response when available. Returns: Community search results in the response data. The documented response schema does not specify individual community fields. Example first-page input: {"keyword":"superman"}.

ae_threads_get_post_detail

Retrieve a Threads post's details by its numeric ID. Input: post_id is required and must be a digits-only string, for example "3349029093483693129". Supply the post ID, not a post URL. Result: Post detail data that may include the post ID, text, author information, images, videos, like count, and post app metadata. Field availability depends on the returned data.

ae_threads_get_user_info

Look up a Threads user's profile by username. Input: Required string `username`, for example `jlo`. From a profile URL such as https://www.threads.net/@jlo, use only `jlo`, not the full URL. Result: The response's `data` contains the user's profile information. It may include `pk` (user ID), `username`, `full_name` (display name), `biography`, `profile_pic_url` (profile image URL), `follower_count`, `is_verified` (verification status), and `bio_links` (links in the biography). Available fields may vary, and `data` may be null. This tool retrieves profile information, not posts or follower lists.

ae_threads_get_user_info_by_id

Look up a Threads user's profile by user ID. Input: - user_id (required string): The Threads user ID, for example "67027868801". You can obtain this ID from user profile or post data. Returns: - A response whose data field contains user information. Documented profile fields include pk (user ID), username, full_name (display name), biography, profile_pic_url (profile image URL), follower_count, is_verified (verification status), and bio_links (links in the biography). - The data field may be null; individual profile fields may vary or be absent. Use this tool when you already have the user ID. It does not search by username or retrieve posts.

ae_threads_get_user_posts

Retrieve the available posts for a Threads user. Inputs: - user_id (required string): The Threads user ID, for example "63625256886". It can be obtained from a user profile lookup. - end_cursor (optional string): Reserved and currently ignored. Omit it; pagination is not supported. Results: The response data includes threads (the post list), next_cursor (always null), and has_more (an indicator of more data, not a usable pagination signal). Post entries may include the post ID, text, author information, image and video information, like count, and post application information. Limitations: A single call returns the available set, typically about 25 posts. This is not a guaranteed complete posting history. No additional pages can be retrieved with this tool, regardless of end_cursor or has_more. Example input: {"user_id":"63625256886"}

ae_threads_get_user_replies

## Get a Threads user's replies Retrieve the replies made by a specified Threads user. ### Inputs - `user_id` (required string): The Threads user ID, for example `"63625256886"`. - `end_cursor` (optional string): Reserved and currently has no effect. Omit it; pagination is not supported. ### Results The response data includes: - `threads`: The user's reply list. - `next_cursor`: Always `null`; no next-page cursor is available. - `has_more`: Indicates whether more data exists, but cannot be used to fetch another page. ### Limitations A single call returns the available batch, approximately 25 items. This is not a guarantee of the user's complete reply history, and additional pages cannot be retrieved. This tool retrieves replies made by the user, not replies to a specified post. ### Example input `{"user_id":"63625256886"}`

ae_threads_get_user_reposts

Retrieve a Threads user's repost list. Inputs: - user_id (required string): The Threads user ID, for example "63625256886". - end_cursor (optional string): Reserved and has no effect. Omit it; pagination is not supported. Results: The response data includes threads (the repost list), next_cursor (always null), and has_more (a more-data indicator that cannot be used to fetch another page). Limitations: One call returns all reposts available through this operation, approximately 25 items. This is not a guarantee of the user's complete repost history. Additional pages cannot be retrieved, even if has_more indicates more data.

ae_threads_search_profiles

Search for Threads user profiles by keyword. Input: query is a required string containing the search keyword, for example "mark". Returns: Search result data containing a users list. Profiles may include a user ID (pk), username, full name (full_name), profile picture URL (profile_pic_url), verification status (is_verified), and follower count (follower_count). Available fields can vary; the result schema does not guarantee every listed profile field. Results identify matching profiles, not posts.

ae_linkedin_get_post_comments

Retrieve comments on a LinkedIn post by its activity identifier. Inputs: - urn (required string): the numeric activity identifier from the post URL, for example "7267273010393358336" from .../urn:li:activity:7267273010393358336/. - sort_by (optional): "Most relevant" (default) or "Most recent". - page (optional integer): page number, starting at 1. - pagination_token (optional string): use the token returned by the previous response when fetching another page. - share_urn (optional string): an additional share URN for a shared post. Returns comment data, which may include commenter details, text, time, pinned status and replies. The documented result includes data for the comments, pagination_token for the next page and total for the number of items returned in this response; total is not the post's overall comment count. Each call retrieves a page rather than necessarily all comments. Intermittent 400 or other errors may be transient. Up to three retries are recommended for transient failures; retries are not guaranteed to resolve every error.

ae_linkedin_get_post_detail

## Purpose Retrieve the details of a LinkedIn post or article by URL. ## Input - `url` (required, string): The full LinkedIn post or article URL. Supported URL forms include `/posts/...` and `/pulse/...`. ## Result Returns response data that may include body text, author information, publication time, hashtags, images or video, and engagement counts. The data payload does not have a fixed documented field structure and may be null; individual details are not guaranteed to be present. This tool looks up a specified URL; it does not search for posts or list a profile's posts.

ae_linkedin_get_user_posts

Retrieve recent LinkedIn activity by member profile URL. Inputs: - url (required): The member's LinkedIn profile URL. - type (optional): posts for posts/reposts (default), comments for posts the member commented on, or reactions for posts the member liked/reacted to. - start and pagination_token (optional): Have no pagination effect; omit them. Returns: A post list in data containing up to 50 recent items, plus paging metadata (count, start, pagination_token). For comments and reactions, the returned items are posts the member interacted with, not a standalone list of comments or reactions. Limitations: Only the most recent 50 items are available. Pagination is not supported, even if paging.pagination_token is populated. Reusing the token returns the same first page and the token does not advance; start also has no effect. Do not use these parameters in a pagination loop. Reliability: Temporary 400 or other errors may occur. Up to 3 retries are recommended for transient failures; retries do not guarantee success. Example: url = "https://www.linkedin.com/in/williamhgates/", type = "posts".

ae_xigua_fetch_user_info

Look up a Xigua Video user's personal information. Input: user_id is required and must be a string containing the target user's ID, for example "52712347586". Returns: a response containing the user's personal information in data. The detailed profile fields are not specified, and data may be null; interpret the information actually returned.