SendIt

Get Analytics

get_analytics

Read-onlyIdempotent

Get engagement analytics for a platform. Facebook and TikTok can include account-wide posts not published through SendIt; unresolved TikTok inbox-draft deliveries may appear as placeholders until SendIt can link them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>"
    },
    "name": "get_analytics"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional maximum posts to return. Facebook feed scanning is capped at 1,000 posts.
`endDate`	No	Optional end date (YYYY-MM-DD).
`team_id`	No	Team ID to get team analytics. If omitted, gets personal analytics.
`platform`	Yes	Platform to get analytics for
`startDate`	No	Optional start date (YYYY-MM-DD). For Facebook, omit this to scan up to 2 years of Page feed history.

Output Schema

Name	Required	Description	Default
`isError`	No
`rawText`	No
`success`	No
`summary`	No
`warning`	No
`platform`	No
`topPosts`	No
`warnings`	No
`dateRange`	No
`errorMessage`	No
`followUpSuggestions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "dateRange": {
+      "additionalProperties": true,
+      "properties": {
+        "from": {
+          "type": "string"
+        },
+        "to": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "errorMessage": {
+      "type": "string"
+    },
+    "followUpSuggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "type": "boolean"
+    },
+    "platform": {
+      "enum": [
+        "x",
+        "linkedin",
+        "linkedin-page",
+        "facebook",
+        "instagram",
+        "threads",
+        "bluesky",
+        "mastodon",
+        "nostr",
+        "youtube",
+        "tiktok",
+        "lemmy",
+        "discord",
+        "slack",
+        "telegram",
+        "pinterest",
+        "dribbble",
+        "devto",
+        "hashnode",
+        "gmb",
+        "whop",
+        "producthunt"
+      ],
+      "type": "string"
+    },
+    "rawText": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "summary": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "topPosts": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "warning": {
+      "type": "string"
+    },
+    "warnings": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedMay 11, 2026

addedInput schema / properties / endDate

Added value: +{
+  "description": "Optional end date (YYYY-MM-DD).",
+  "format": "date",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Optional maximum posts to return. Facebook feed scanning is capped at 1,000 posts.",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "number"
+}

addedInput schema / properties / startDate

Added value: +{
+  "description": "Optional start date (YYYY-MM-DD). For Facebook, omit this to scan up to 2 years of Page feed history.",
+  "format": "date",
+  "type": "string"
+}

First observedMay 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context: Facebook and TikTok can include account-wide posts not published through SendIt, and unresolved TikTok inbox-draft deliveries may appear as placeholders. This warns about potentially unexpected data, going beyond the safety annotations.

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 two sentences long: the first states the main purpose, the second adds important caveats. There is no wasted text and the key action is front-loaded.

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?

With an output schema present and robust annotations, the description covers the most important quirks (Facebook/TikTok account-wide posts, TikTok placeholders) that affect interpretation of results. It does not explain team vs personal analytics, but that is covered by the schema. Overall, it is sufficiently complete for a read-only analytics tool.

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?

The schema provides 100% coverage with descriptions for platform, limit, startDate, endDate, and team_id. The description adds no additional parameter-level meaning beyond what the schema already gives, so the baseline of 3 applies.

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

Purpose4/5

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

The description clearly states the core action and resource: 'Get engagement analytics for a platform.' It does not explicitly differentiate from sibling tools like get_post_analytics or get_unified_analytics, but the focus on per-platform analytics and the platform-specific caveats imply the tool's scope.

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 such as get_post_analytics, get_unified_analytics, or list_analytics_reports. The description only mentions Facebook/TikTok behavioral caveats; it never states preferred use cases, exclusions, or relationships to other analytics tools.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.