Post Stats

List a channel's latest posts

list_channel_stats

Read-onlyIdempotent

List the latest posts of a YouTube channel with the view count its public channel page shows, newest Shorts first, then videos. For a TikTok profile it returns followers, total likes and video count (TikTok's public profile page lists no videos). An X profile is refused with the reason.

Input Schema

Name	Required	Description	Default
`limit`	No	Most recent posts to return. Default 20.
`channel`	Yes	A YouTube channel ("https://www.youtube.com/@handle") or a TikTok profile ("https://www.tiktok.com/@user").

Output Schema

Name	Required	Description
`as_of`	Yes	ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.
`error`	No
`notes`	No
`posts`	No
`source`	Yes	Who the data comes from, to cite and to check it against.
`status`	Yes
`totals`	No
`channel`	Yes
`from_cache`	No
`totals_sources`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

addedOutput schema / properties / as_of

Added value: +{
+  "description": "ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.",
+  "type": "string"
+}

addedOutput schema / properties / source

Added value: +{
+  "description": "Who the data comes from, to cite and to check it against.",
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "url"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "status",
-  "channel"
-]New value: +[
+  "status",
+  "channel",
+  "as_of",
+  "source"
+]

First observedOct 16, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond that: the view count is the one the public channel page shows, results are ordered Shorts first then videos, and TikTok yields profile aggregates rather than posts. Missing minor details like behavior when a URL is malformed or pagination beyond limit.

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?

Three tight sentences, each carrying a distinct fact (YouTube result shape and ordering, TikTok result shape, X refusal), with the primary use case front-loaded and no filler.

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?

An output schema exists, so return values needn't be spelled out, and annotations cover safety. The description fills the remaining gap that matters — platform-dependent behavior — but leaves the name/title ambiguity and sibling selection unresolved, which is the one thing an agent could still get wrong.

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?

Schema description coverage is 100%, with both limit (default 20, max 50) and channel (YouTube/TikTok URL forms) documented in the schema. The description restates the supported URL forms but says nothing new about limit or ordering interactions, so it sits at the baseline.

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 names a specific verb and resource and goes further by defining per-platform return shapes: YouTube latest posts with view counts, TikTok follower/like/video counts, X refused. The only weakness is that the name (list_channel_stats) and title (latest posts) pull in two directions and the description covers both, so an agent must read the body to know what it actually gets.

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?

It does state a negative case worth knowing (X profiles are refused) and implies the tool is for channel/profile-level overviews, but it never mentions the obvious siblings get_post_stats or compare_posts, so the agent gets no explicit routing for when a single-post lookup or a comparison is the better call.

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

All Post Stats 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.