sprout-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPROUT_API_TOKEN | Yes | Your Sprout Social API token. Generate in Sprout under Settings > Global Features > API. | |
| SPROUT_CUSTOMER_ID | No | Optional customer ID. If unset, the server infers it from the token (only works if token sees exactly one customer). |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_customer_idA | List the Sprout customer IDs this API token can access. Use when SPROUT_CUSTOMER_ID is unknown or you need to confirm which Sprout account the token points at. Returns customer_id and name for each. |
| list_profilesA | List the social profiles connected to this Sprout customer. Start here: every analytics call is scoped by customer_profile_id, and this is the only place those IDs come from. Each profile includes customer_profile_id, network_type (facebook, instagram, tiktok, linkedin, twitter, youtube, pinterest, threads, bluesky), name, native_name and native_id. |
| get_profile_metricsA | Pull profile-level analytics for a date range (daily granularity). Args:
profile_ids: customer_profile_id values from list_profiles. Max 100.
start_date: inclusive start, YYYY-MM-DD.
end_date: exclusive end, YYYY-MM-DD. Range must be <= 1 year.
metrics: metric keys to request, e.g. ["impressions",
"lifetime_snapshot.followers_count", "net_follower_growth"]. Keys are
network-specific -- call list_metrics to see valid ones. Omit to let
Sprout return its defaults.
page: 1-based page to start from.
all_pages: follow pagination and concatenate the Returns the API response verbatim: each record has Note: rates such as engagement rate are NOT returned by Sprout -- they are derived. Compute them downstream from the raw counts. |
| get_post_performanceA | Pull post-level analytics for posts created in a datetime range. Args:
profile_ids: customer_profile_id values from list_profiles. Max 100.
start_datetime: inclusive, YYYY-MM-DDTHH:MM:SS (e.g. 2026-06-01T00:00:00).
end_datetime: inclusive, YYYY-MM-DDTHH:MM:SS (e.g. 2026-06-30T23:59:59).
metrics: post metric keys, mostly prefixed Returns the API response verbatim -- one record per post, carrying whichever fields and metrics were requested. Useful for per-post label/tag analysis. |
| list_metricsA | Look up valid Sprout metric keys for a network, so calls don't guess. Args: network: one of facebook, instagram, tiktok, linkedin, x, youtube, pinterest, threads, bluesky. Omit to list every network. scope: "profile" (for get_profile_metrics), "post" (for get_post_performance), or "all". Each entry gives the human-readable name, the API key to send, and whether it needs Premium Analytics. Also lists Sprout's calculated metrics -- these are NOT returned by the API and must be derived from the raw counts. This catalog was generated from the published docs; if the API rejects a key, check the live docs at https://api.sproutsocial.com/docs/. |
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 serves a distinct purpose: customer ID discovery, profile listing, metric metadata, profile analytics, and post analytics. There is no functional overlap, and descriptions clearly differentiate them.
Tools follow a 'verb_noun' pattern, but verbs are inconsistent: 'get_customer_id' returns a list (could be 'list'), while 'list_profiles' and 'list_metrics' use 'list'. However, the pattern is otherwise consistent and readable.
Five tools cover the essential operations for a social media analytics server: account discovery, profile enumeration, metric exploration, and two data retrieval endpoints. This is well-scoped and not excessive.
The set covers core analytics workflows (profile metrics, post performance) and necessary metadata (customer IDs, profiles, metrics). Minor gaps exist, such as missing a tool to fetch a specific post by ID or account-level aggregation, but these are non-critical for the intended read-only analytics use case.