`social_account_activity`

Pack: social-signal · Endpoint: https://gateway.pipeworx.io/social-signal/mcp

POSTING CADENCE for one social media account as a TIME SERIES: posts per day over a window, plus average engagement per post and the timestamp of the most recent post. Answers “how often does this account post”, “has this account gone quiet”, “what is their POST VOLUME TREND”, “how active is @someone on social media”. The network is inferred from the handle shape (a dotted handle is Bluesky, “@[email protected]” is Mastodon, “u/name” is Reddit); when the shape is ambiguous the response lists every network tried in networks_tried. Days with a null count were outside the reach of the feed and stay distinguishable from days with a measured zero.

Parameters

Name	Type	Required	Description
`handle`	string	yes	The account handle. Bluesky: “user.bsky.social” or a did:. Mastodon: “@[email protected]”. Reddit: “u/name”. A bare name is tried against each in turn.
`days`	number	no	How many days of cadence to report. Default 30, maximum 90.

Example call

Arguments

{
  "handle": "bsky.app",
  "days": 30
}

curl

curl -X POST https://gateway.pipeworx.io/social-signal/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"social_account_activity","arguments":{"handle":"bsky.app","days":30}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('social_account_activity', {
  "handle": "bsky.app",
  "days": 30
});

More examples

{
  "handle": "@[email protected]",
  "days": 90
}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "social-signal": {
      "url": "https://gateway.pipeworx.io/social-signal/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

social_account_activity