Skip to main content
Glama

aidelly

by io.github.wilzer
OverviewDiscussionsAdmin

Get Analytics Insights

aidelly_get_analytics_insights
Read-onlyIdempotent

Read saved analytics insights for the workspace. May return an empty list. Reading generates nothing (aidelly_generate_analytics_insights does), and saved insights are not limited to the analytics summary date range, so a missing or stale insight is not evidence of a trend. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
limitNo
queryNoOptional query overrides for endpoints with sparse parameter schemas.
cursorNo
brand_idNo
dismissedNo
platformsNo
workspace_idNoWorkspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / workspace_id / description
      Previous 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."
  2. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "maxLength": 512,
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / workspace_id / description
      Added 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."
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds real behavioral context: an empty list is a valid outcome, and a missing/stale insight must not be read as evidence of a trend. The closing 'Read-only' merely restates the annotation, adding no value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action and then the two most likely misinterpretations. Only the trailing 'Read-only.' is expendable, duplicating the readOnlyHint annotation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It covers the semantic trap (empty results vs. trend evidence) but leaves the 8-parameter surface, including the opaque nested query object, undocumented with no output schema to fill in. Adequate for the behavioral warning, incomplete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% across 8 parameters, including a free-form nested 'query' object and an undocumented 'type' string, so the description carries the burden of compensating. It says nothing about any parameter — no meaning for type, platforms, dismissed, brand_id, or how cursor/limit paginate. A significant gap.

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?

States a specific verb+resource ('Read saved analytics insights for the workspace') and explicitly distinguishes itself from its nearest sibling, aidelly_generate_analytics_insights, which it names. An agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context: reading generates nothing (the generate sibling does), and results may legitimately be empty because saved insights are not scoped to the analytics summary date range. It does not, however, contrast with other read siblings such as aidelly_get_analytics_summary or aidelly_get_analytics_unified, so selection guidance is incomplete.

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

All aidelly 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