SendIt

Get Unified Analytics

get_unified_analytics

Read-only

Get cross-platform analytics combining organic and paid performance.

Aggregates metrics across all connected platforms into a single view. Supports time-series breakdowns and platform comparison.

Input Schema

TableJSON Schema

Name	Required	Description
`endDate`	Yes	End date (YYYY-MM-DD)
`breakdown`	No	Breakdown dimension
`platforms`	No	Filter to specific platforms (optional, all if omitted)
`startDate`	Yes	Start date (YYYY-MM-DD)
`includePaid`	No	Include paid metrics (default true)
`includeOrganic`	No	Include organic metrics (default true)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedMay 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds behavioral context about aggregating metrics across platforms and supporting breakdowns, but it does not disclose return format, data freshness, or platform coverage details.

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

Conciseness5/5

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

The description is three short sentences with no filler. It front-loads the core purpose in the first sentence and keeps additional details concise, making it easy to parse quickly.

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

Completeness3/5

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

For a moderate-complexity analytics tool with no output schema, the description explains the core aggregation function but lacks details about response structure, data refresh behavior, or differentiation from sibling analytics tools. It is adequate but not rich enough to fully orient the agent without additional context.

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

Parameters3/5

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

All 6 parameters have schema descriptions (100% coverage), so the schema carries the parameter documentation. The description's mention of time-series breakdowns and platform comparison weakly maps to the breakdown and platforms parameters, but it adds no new semantic detail beyond what the schema already provides.

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 gets cross-platform analytics combining organic and paid performance. It uses a specific verb ('Get') and resource ('unified analytics'), and distinguishes itself from single-platform analytics tools by emphasizing aggregation across all connected platforms.

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

Usage Guidelines3/5

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

The description implies use when a cross-platform overview is needed, but it does not explicitly say when to use this tool versus alternatives like get_analytics or get_unified_ad_report. No exclusions or alternative tool names are mentioned, leaving the agent to infer the appropriate context.

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

All SendIt tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0

Disambiguation2/5

With 148 tools, there is significant overlap. For example, generate_content, publish_ai, generate_post_bundle, and request_project_content all generate content; get_analytics, get_unified_analytics, get_post_analytics, get_ad_performance, and get_unified_ad_report all fetch performance metrics; and list_inbox vs list_conversations blur comment and conversation management. Descriptions help, but boundaries between tools are often unclear.

Naming Consistency3/5

Most tools follow a verb_noun pattern (e.g., list_teams, create_goal, delete_post), but there are notable deviations: create_library_item vs save_to_library, publish_content vs publish_ai, schedule_content vs schedule_content_advanced, and connect_platform vs connect_connector. Mixed prefixes like 'autopilot_', 'check_', and 'get_' are fine, but overlapping verbs and a hyphen in 'connect_linkedin-page' reduce consistency.

Tool Count1/5

148 tools is extreme for any server. Even for a broad social media management platform, this is far beyond what an agent can effectively navigate. The count is unwieldy and suggests the surface should be split into multiple focused servers (publishing, analytics, connectors, workflows, etc.).

Completeness3/5

The core social publishing workflow is well covered (create, schedule, publish, edit, delete, retry), and there are extensive features for analytics, workflows, connectors, and AI agents. However, some resources have CRUD gaps: no update/delete for brand voices, no delete_project, no update/delete for Product Hunt goals, and no explicit get_workflow. These are workable but notable omissions.

Resources

Need Help?