pulse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PULSE_API_URL | No | Override the backend URL for Pulse API | https://pulse.walls.sh |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| metricsA | Get a public social post's metrics. Give a post URL (YouTube, X/Twitter incl. view counts, TikTok incl. photo posts, Bluesky, Mastodon (major instances), Instagram, Threads, LinkedIn — short links like vm.tiktok.com and t.co resolve automatically) and get normalized { platform, views, likes, comments, shares, quotes, bookmarks, publishedAt, title, author, thumbnail } — shares = reshares (X retweets, TikTok shares, Bluesky reposts); quotes = quote posts (X, Bluesky); bookmarks = saves (X). Free. |
| metrics_batchA | Get metrics for many posts and/or profiles in one call. Pass an array of URLs (max 50, mixed post and profile URLs welcome); returns { count, results }, order preserved — each result is the metrics object or { url, error }. |
| historyA | Get the recorded metrics history of a post OR a profile — the growth curve. Every fresh metrics fetch records a { t, views, likes, comments, shares, quotes, bookmarks } snapshot (profiles: { t, followers, posts }); this returns the series (oldest first). Pass |
| profileA | Get account-level metrics for a profile URL — { platform, handle, name, followers, following, posts, likes, verified, avatar }. Live: YouTube channels (subscribers), TikTok users (exact counts + total hearts), Instagram accounts (exact counts), X accounts (followers/following/posts), Bluesky accounts (exact counts), Mastodon accounts (exact, major instances). Threads/LinkedIn profiles need a login. |
| profile_batchA | Get account-level metrics for many profile URLs in one call — same as |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: single metrics vs historical series vs batch metrics vs single profile vs batch profile. No overlap in functionality.
Consistent noun naming for singletons (metrics, profile, history) and noun_batch for batch variants (metrics_batch, profile_batch). Clear and predictable pattern.
5 tools cover the core operations for social media metrics retrieval: single and batch for posts and profiles, plus history. Well-scoped without excess.
Covers essential retrieval operations, but lacks an explicit endpoint to list supported platforms or trigger a refresh. Minor gap for an otherwise complete surface.