Multi Upload Tool

get_analytics

Read-only

Read published-post performance: views, likes, comments, shares, plus growth over the last 30 days. summary compares the last 30 days with the 30 before (views gained, follower change, posts published; null = not measured, never 0) and followerHistory gives one follower total per day. Call with no argument for every account at once, with accountId for one account, or with postId for a single post. Numbers come from a nightly sync, so they lag the platform by up to a day — lastRefreshedAt says when they were last measured, and a metric a platform does not report comes back as 0. Account and global calls also return bestTimes: the weekday and hours whose posts averaged the most views, to feed scheduledAt in create_post. This is read-only; it never publishes.

Input Schema

Name	Required	Description
`limit`	No	How many top posts to return (default 10). Ignored with postId.
`postId`	No	postId of one post (from create_post or list_recent_posts). Returns that post's metrics only.
`source`	No	Which posts topPosts ranks: all (default), mut (published through Multi Upload Tool) or external (posted directly on the platform). Totals and summary always cover every post.
`timezone`	No	IANA timezone the bestTimes weekday/hour buckets are read in, e.g. Europe/Paris. Defaults to UTC — always pass the user's own zone, because an hour-of-day ranking read in the wrong zone is silently off by the whole offset.
`accountId`	No	Connected account id (from list_accounts). Omit for all accounts combined.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 15, 2026

addedInput schema / properties / accountId / minLength
```
Added value: +1
```

addedInput schema / properties / postId / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "minLength": 1,
+    "type": "string"
+  }
+]

removedInput schema / properties / postId / oneOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "string"
-  }
-]

addedInput schema / properties / timezone / minLength
```
Added value: +1
```

First observedOct 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover readOnlyHint/openWorldHint, but the description adds substantial behavior: nightly-sync lag, lastRefreshedAt as the measurement timestamp, and the null-vs-0 distinction ('null = not measured, never 0' / 'a platform does not report comes back as 0'). It also flags the timezone-offset pitfall that silently corrupts bestTimes. This is real behavioral disclosure beyond the structured fields.

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?

Front-loaded with return contents, then invocation modes, then freshness caveats. Every sentence carries information, but it is a dense single block; the caveats about sync lag and null-vs-0 could be tightened.

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

Completeness5/5

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

With no output schema, the description carries the full burden of explaining return shape and it does so: summary semantics, followerHistory granularity, lastRefreshedAt, bestTimes shape and purpose. An agent has everything needed to call and interpret the tool correctly.

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?

Schema coverage is 100%, so the 3 baseline applies, but the description adds meaning the schema lacks: the no-argument/accountId/postId selection logic, that source only affects topPosts ranking while 'Totals and summary always cover every post', and the warning to always pass the user's zone. Marginal but genuine value on top of an already-complete 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?

States a specific verb+resource immediately ('Read published-post performance: views, likes, comments, shares, plus growth over the last 30 days') and enumerates the exact artifacts returned (summary, followerHistory, bestTimes). An agent can distinguish it from siblings like get_post_status or list_recent_posts without opening the schema.

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

Usage Guidelines4/5

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

Explicitly maps invocation modes to intent: 'Call with no argument for every account at once, with accountId for one account, or with postId for a single post', and names create_post as the downstream consumer of bestTimes. It does not state when NOT to use it versus siblings such as get_post_status, so the exclusion side is missing.

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

All Multi Upload Tool 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.

Resources

Need Help?