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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/patwalls/pulse-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server