Skip to main content
Glama

get_messages

Retrieve inbound social media messages with filtering options to monitor mentions, DMs, and comments across Sprout Social profiles.

Instructions

Retrieve inbound inbox messages (Smart Inbox) with optional filtering.

This endpoint returns INBOUND messages only (mentions, DMs, comments).
For OUTBOUND post counts and performance metrics, use get_post_analytics instead.

Args:
    profile_ids: Comma-separated Sprout profile IDs.
    start_time: Start datetime (ISO 8601, e.g. '2024-01-01T00:00:00').
    end_time: End datetime (ISO 8601).
    tag_ids: Comma-separated tag IDs to filter by (optional).
    limit: Number of messages to return (default 50).
    page_cursor: Pagination cursor from a previous response (optional).
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_idsYes
start_timeYes
end_timeYes
tag_idsNo
limitNo
page_cursorNo
customer_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the tool's read-only nature implicitly through 'retrieve' and specifies the data scope (inbound messages). However, it doesn't mention rate limits, authentication requirements, error conditions, or pagination behavior beyond cursor parameter existence. Some behavioral context is missing for a tool with 7 parameters.

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 appropriately sized and well-structured with purpose statement, usage guidance, and parameter documentation. The Args section is organized but could be more front-loaded with critical information. Every sentence adds value, though some parameter explanations could be more concise.

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 (7 parameters, filtering capabilities) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers purpose, differentiation, and parameter semantics well. The main gap is insufficient behavioral context about rate limits, errors, or response structure details not covered by the output schema.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates well by providing semantic meaning for all 7 parameters in the Args section. It explains what each parameter represents (e.g., 'Comma-separated Sprout profile IDs', 'Start datetime (ISO 8601)'), includes format examples, and notes optional/default values. This adds significant value beyond the bare schema.

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 tool's purpose with specific verbs ('retrieve inbound inbox messages') and resources ('Smart Inbox'), including scope details ('inbound messages only - mentions, DMs, comments'). It distinguishes itself from sibling get_post_analytics by specifying inbound vs outbound focus.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool ('for inbound messages only') and when to use an alternative ('for outbound post counts and performance metrics, use get_post_analytics instead'). This gives clear context for tool selection among siblings.

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