Skip to main content
Glama

aidelly

by io.github.wilzer
OverviewDiscussionsAdmin

Get Content Automations

aidelly_get_content_automations
Read-onlyIdempotent

List saved content automation rules for the selected workspace. Returns rule configuration and activity state; follow next_cursor for additional pages. Does not run or change rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional query overrides for endpoints with sparse parameter schemas.
cursorNo
brand_idNo
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

A4/5.0
Behavior4/5

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

With readOnlyHint/idempotentHint already covering the safety profile, the description still adds real value: it discloses what is returned ('rule configuration and activity state') and pagination behavior ('follow next_cursor'). It doesn't mention auth, rate limits, or result volume, so it's not a 5.

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 compact sentences, front-loaded with the purpose, then return content, pagination, and the negative constraint. No filler.

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?

For a 4-param read tool with no output schema, the description covers purpose, return shape, pagination, and the read-only boundary. The only gap is the meaning of brand_id and the nested query override object.

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?

Schema description coverage is 50%, and the description only clarifies the cursor parameter semantics ('follow next_cursor for additional pages') and implies workspace scoping. The brand_id and the nested query override object remain undocumented in both the schema and the description, so it only partially compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List saved content automation rules') with workspace scope, which cleanly separates it from mutation siblings like trigger/update/delete_content_automation. It does not explicitly name its closest sibling (aidelly_get_content_automation, singular), so it falls just short of 5.

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?

The clause 'Does not run or change rules' gives a clear when-not boundary that routes the agent away from aidelly_trigger_content_automation, and the cursor note tells the agent how to continue. It stops short of naming an alternative or stating prerequisites for use.

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