HDW MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HDW_ACCOUNT_ID | Yes | Your HorizonDataWave account ID obtained from app.horizondatawave.ai | |
| HDW_ACCESS_TOKEN | Yes | Your HorizonDataWave API access token obtained from app.horizondatawave.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_linkedin_usersC | Search for LinkedIn users with various filters like keywords, name, title, company, location etc. |
| get_linkedin_profileB | Get detailed information about a LinkedIn user profile |
| get_linkedin_email_userB | Get LinkedIn user details by email |
| get_linkedin_user_postsC | Get LinkedIn posts for a user by URN (must include prefix, example: fsd_profile:ACoAAEWn01QBWENVMWqyM3BHfa1A-xsvxjdaXsY) |
| get_linkedin_user_reactionsC | Get LinkedIn reactions for a user by URN (must include prefix, example: fsd_profile:ACoAA...) |
| get_linkedin_user_commentsC | Get LinkedIn comments for a user by URN (must include prefix, example: fsd_profile:ACoAA...) |
| search_linkedin_postsC | Search for LinkedIn posts with various filters like keywords, content type, authors, etc. |
| search_reddit_postsC | Search for Reddit posts with various filters |
| get_linkedin_chat_messagesC | Get top chat messages from LinkedIn management API. Account ID is taken from environment. |
| send_linkedin_chat_messageC | Send a chat message via LinkedIn management API. Account ID is taken from environment. |
| send_linkedin_connectionC | Send a connection invitation to LinkedIn user. Account ID is taken from environment. |
| send_linkedin_post_commentB | Create a comment on a LinkedIn post or on another comment. Account ID is taken from environment. |
| get_linkedin_user_connectionsC | Get list of LinkedIn user connections. Account ID is taken from environment. |
| get_linkedin_post_repostsC | Get LinkedIn reposts for a post by URN |
| get_linkedin_post_commentsC | Get LinkedIn comments for a post by URN |
| get_linkedin_post_reactionsB | Get LinkedIn reactions for a post by URN |
| get_linkedin_google_companyC | Search for LinkedIn companies using Google search. First result is usually the best match. |
| get_linkedin_companyC | Get detailed information about a LinkedIn company |
| get_linkedin_company_employeesC | Get employees of a LinkedIn company |
| send_linkedin_postC | Create a post on LinkedIn. Account ID is taken from environment. |
| linkedin_sn_search_usersC | Advanced search for LinkedIn users using Sales Navigator filters |
| get_linkedin_conversationsC | Get list of LinkedIn conversations from the messaging interface. Account ID is taken from environment. |
| google_searchC | Search for information using Google search API |
| get_instagram_userC | Get Instagram user information by URL, alias or ID |
| get_instagram_user_postsC | Get Instagram user posts |
| get_instagram_post_commentsC | Get Instagram post comments |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| LinkedIn users for "software engineer" | LinkedIn user search results including name, headline, and location |
TDQS
Scored across 26 tools
Most tools have distinct purposes targeting specific platforms (Instagram, LinkedIn, Google, Reddit) and actions (get, search, send). However, there is some overlap between get_linkedin_profile and get_linkedin_email_user, as both retrieve LinkedIn user details, which could cause minor confusion. Overall, the tool boundaries are clear with minimal ambiguity.
Tool names follow a highly consistent verb_noun pattern throughout, such as get_instagram_user, search_linkedin_posts, and send_linkedin_chat_message. All tools use snake_case with clear action prefixes (get, search, send), making them predictable and easy to understand. There are no deviations in naming conventions.
With 26 tools, the count is borderline high for a social media data and interaction server, leaning towards heavy. While it covers multiple platforms and actions, the number may feel overwhelming for an agent to navigate efficiently. A more focused set could improve usability without sacrificing functionality.
The tool set provides comprehensive coverage for LinkedIn operations, including CRUD-like actions (get, search, send) for profiles, posts, comments, and messages, with minor gaps such as updating or deleting LinkedIn content. Instagram and Reddit tools are more limited (only get/search), but the server's primary focus on LinkedIn is well-covered for core workflows.