list_accounts
List all tracked creator accounts. Free.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Reel25 — Video Analytics for TikTok, Instagram & YouTube
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so description carries the burden. It clearly states a read/list operation and mentions 'Free' (no credits), but lacks details like response format or pagination. Adequate for a simple list.
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?
Two short sentences, front-loaded, no wasted words.
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?
Simple tool with no schema/output schema; description covers core functionality but doesn't mention return values. Nearly complete for a trivial list 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 tool has zero parameters, so the description doesn't need to explain them; baseline 4 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 uses a specific verb 'list' with a clear resource 'all tracked creator accounts', distinguishing it from singular get_account and video-oriented tools like list_videos.
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 on when to use this tool vs alternatives; 'Free' implies no cost but doesn't explicitly state conditions or exclusions.
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.5/5.0
Disambiguation5/5
Every tool targets a distinct resource and action: account vs video vs folder vs analysis vs radar. Even similar tools like analyze_video and get_analysis are clearly separated by creation vs retrieval.
Naming Consistency4/5
Most names follow a verb_noun pattern (track_video, get_account, create_folder). Minor deviations like 'growth_trends' and 'radar_history' are noun phrases but remain readable and predictable.
Tool Count4/5
26 tools is slightly above the ideal range, but the server covers a broad domain with distinct sub-areas (accounts, videos, folders, analytics, AI analysis, radar), so the count is justified rather than bloated.
Completeness4/5
Core lifecycle operations are covered: track/untrack accounts and videos, list/get details, analytics, folders, and AI analysis. Minor gaps exist (no delete folder, no remove-from-folder), but they don't break primary workflows.