viddler_analytics_account_usage
Return the authenticated account's plan, quota used/remaining, and video count.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Viddler
by com.viddler
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full burden. It indicates a read-only operation returning specific data. However, it does not disclose behavioral traits like authentication requirements, rate limits, or idempotency.
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?
A single, front-loaded sentence with zero wasted words. Every piece of information is relevant and earned.
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?
The tool has no parameters or output schema, and the description explains the return data. It is sufficient for the agent's purpose, though it could be more explicit about authentication context and return format. Nearly complete for a simple tool.
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?
The input schema has no parameters (empty object, 100% coverage). With 0 parameters, baseline is 4. The description adds value by specifying the return data (plan, quota, video count), which is beyond the schema's empty properties.
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 uses a specific verb ('Return') and clearly states the resource ('authenticated account's plan, quota used/remaining, and video count'). It distinguishes from siblings like 'viddler_analytics_get_views' and 'viddler_videos_list' by focusing on account-level usage.
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?
No explicit guidance on when to use this tool versus alternatives. The purpose is implied as the go-to for account-level analytics, but no exclusions or when-not-to-use scenarios are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.8/5.0
Disambiguation5/5
Each tool targets a specific action on a distinct resource (access, analytics, feedback, videos). There is no overlap; for example, password protection and custom URL are clearly separate access tools.
Naming Consistency5/5
All tools follow the pattern `viddler_<category>_<verb>_<noun>` with consistent snake_case. Categories are logical (access, analytics, feedback, videos) and verbs are appropriately descriptive (remove, set, get, list, create, etc.).
Tool Count4/5
12 tools is a reasonable number for a video management server. The set is scoped to core operations, not bloated. A few more could be added (e.g., delete), but the count is appropriate for the domain.
Completeness3/5
The tool set covers upload, registration, retrieval, listing, and metadata updates, but lacks a delete video tool. This is a notable gap for a video management server. Other missing operations like trash or restore are not critical, but delete is a basic lifecycle operation.