Skip to main content
Glama

VidGuy

by ai.vidguy
OverviewDiscussionsAdmin

Hosted accounts performance pulse

get_managed_accounts_pulse
Read-only

Roll-up of ALL your hosted / managed accounts' performance over the last 7, 14, 30 or 90 days: total views/likes/comments/shares/posts/followers, the views delta vs the previous period, a per-day and cumulative views series, and how many accounts have metrics yet (accountsWithMetrics/accountsTotal, capturedAt). Served from cached metrics (refreshed about daily) — cheap to call. For one account's breakdown use get_social_analytics with source 'managed_account'. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoWindow in days: 7, 14, 30, 90 (default 30). Any other number rounds up to the next supported window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / days / anyOf
      Previous value: -[
-  {
-    "const": 7,
-    "type": "number"
-  },
-  {
-    "const": 30,
-    "type": "number"
-  },
-  {
-    "const": 90,
-    "type": "number"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
    • addedInput schema / properties / days / description
      Added value: +"Window in days: 7, 14, 30, 90 (default 30). Any other number rounds up to the next supported window."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive behavior. The description adds valuable context beyond those: metrics are cached and refreshed about daily, and it exposes the accountsWithMetrics/accountsTotal/capturedAt fields to clarify staleness/coverage semantics.

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?

Every sentence earns its place: purpose and scope, metric contents, cache/cost caveat, and the sibling tool alternative. The description is dense but not padded, and the essential differentiating information appears early.

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?

There is no output schema, but the description compensates by enumerating the returned aggregates, the delta, the time series, and the accounts-with-metrics coverage fields. With a single well-documented parameter and clear response contents, nothing needed to invoke the tool correctly is missing.

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 input schema already fully documents the days parameter, supported windows, default, and rounding behavior. The description restates the window options but does not add meaning beyond what the schema provides, so the baseline of 3 applies.

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 opens with 'Roll-up of ALL your hosted / managed accounts' performance' — a specific verb, resource, and scope. It clearly distinguishes the aggregate tool from the per-account 'get_social_analytics' sibling by naming it explicitly.

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?

It states the tool is for a roll-up of all managed accounts and explicitly routes the agent to get_social_analytics with source 'managed_account' when a single account breakdown is needed. It also adds cost guidance ('cheap to call', 'Free').

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

All VidGuy toolsInspect
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