Skip to main content
Glama
jmeserve

sprout-mcp

by jmeserve
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_profile_analytics

Retrieve aggregated social media analytics for specified profiles, including metrics like impressions, engagements, and follower growth within custom date ranges.

Instructions

Get analytics metrics aggregated by social profile.

Args:
    profile_ids: Comma-separated Sprout profile IDs.
    start_time: Start of period (ISO 8601, e.g. '2024-01-01T00:00:00').
    end_time: End of period (ISO 8601, e.g. '2024-01-31T23:59:59').
    metrics: Comma-separated metric names. Common options:
             impressions, engagements, net_follower_growth, engagement_rate,
             video_views, reactions, comments, shares, clicks.
    timezone: Timezone for the report (e.g. 'America/Chicago'). Default: UTC.
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_idsYes
start_timeYes
end_timeYes
metricsNoimpressions,engagements,net_follower_growth
timezoneNoUTC
customer_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool's function and parameters but lacks critical behavioral details such as whether this is a read-only operation, rate limits, authentication requirements, or error handling. The description doesn't compensate for the absence of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and appropriately sized, with a clear opening sentence followed by a parameter breakdown. Each parameter explanation is concise and adds value, though the list format could be slightly more front-loaded for immediate clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, no annotations) and the presence of an output schema, the description is mostly complete. It thoroughly documents parameters and their semantics, which is critical since the schema lacks descriptions. However, it misses behavioral context like rate limits or authentication, slightly reducing completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant meaning beyond the input schema, which has 0% description coverage. It explains each parameter's purpose, format (e.g., 'comma-separated', 'ISO 8601'), provides examples for 'start_time' and 'end_time', lists common metric options with details, and notes defaults for 'timezone' and 'customer_id'. This fully compensates for the schema's lack of descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get analytics metrics aggregated by social profile') with the resource ('social profile'), distinguishing it from siblings like 'get_post_analytics' which focuses on posts rather than profiles. The verb 'Get' combined with 'analytics metrics' and 'aggregated by social profile' provides precise purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'get_post_analytics' or other analytics-related tools. The description lists parameters but doesn't explain the tool's context or prerequisites, leaving the agent without usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

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/jmeserve/sprout-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server