aidelly_list_viral_trendsList discovered viral trends for the workspace, ordered by virality score.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | Optional query overrides for endpoints with sparse parameter schemas. | |
| cursor | No | ||
| offset | No | ||
| status | No | ||
| brand_id | No | ||
| workspace_id | No | Workspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content. |
Changes observed during successful MCP inspections.
Input schema / properties / workspace_id / descriptionPrevious value: -"Workspace to operate in. Do not ask the user for this UUID — call aidelly_list_workspaces and use the `id` of the matching workspace. Optional for read operations; required when creating content."New value: +"Workspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content."Input schema / properties / cursorAdded value: +{
+ "maxLength": 512,
+ "type": "string"
+}Input schema / properties / workspace_id / descriptionAdded value: +"Workspace to operate in. Do not ask the user for this UUID — call aidelly_list_workspaces and use the `id` of the matching workspace. Optional for read operations; required when creating content."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds only the ordering behavior (by virality score); it says nothing about pagination, result volume, freshness, or that 'discovered' trends come from an external source despite openWorldHint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the verb and resource, and the ordering detail is appended efficiently. It wastes no words, though the extreme brevity is under-specification rather than optimal density for a 7-parameter tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 7 parameters, low schema coverage, a nested query object, no output schema, and no annotation gaps filled, the description is too thin. An agent cannot tell how to filter by status or brand, how to paginate, or that the nested query object even exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 29% across 7 parameters. The description mentions the workspace implicitly but never explains limit, cursor, offset, status enum values, brand_id, or the free-form query override object, so it fails to compensate for the documentation gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List discovered viral trends') plus scope ('for the workspace') and order ('by virality score'). It is unique among the siblings (no other tool covers trends), so sibling differentiation is moot, but it stops short of a 5 because it doesn't say what a 'viral trend' record contains or what discovery means.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use or when-not-to-use guidance, nor any named alternative. The agent must infer that this is the read path for trend discovery, and nothing tells it how the tool relates to sibling listing tools or when trending data would be preferred over analytics tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.