Skip to main content
Glama

aidelly

by io.github.wilzer
OverviewDiscussionsAdmin

List Scheduled Posts

aidelly_list_scheduled_posts
Read-onlyIdempotent

List workspace scheduled posts with from/to timestamps, status, platform, and cursor pagination (maximum 100 per page). Returns items with scheduled_at and approval_status; an empty items array means no matching posts. Approval state is separate from publishing status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo
fromNo
limitNo
queryNoOptional query overrides for endpoints with sparse parameter schemas.
cursorNo
statusNo
brand_idNo
platformNoSupported platform identifier. `twitter` and `x` map to the same surface; responses always normalize to `twitter`. `google_business` posts target a single Google Business Profile location identified by `platform_specific.locationName`. `mastodon` accounts are per-instance — the connected account carries its own `instance_url`.
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. Changed5 schema fields changed
    • removedInput schema / properties / campaignId
      Removed value: -{
-  "format": "uuid",
-  "type": "string"
-}
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +25
    • changedInput schema / properties / limit / maximum
      Previous value: -200New value: +100
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "Supported platform identifier. `twitter` and `x` map to the same surface;\nresponses always normalize to `twitter`. `google_business` posts target\na single Google Business Profile location identified by\n`platform_specific.locationName`. `mastodon` accounts are per-instance —\nthe connected account carries its own `instance_url`.\n",
+  "enum": [
+    "facebook",
+    "instagram",
+    "linkedin",
+    "twitter",
+    "bluesky",
+    "threads",
+    "pinterest",
+    "youtube",
+    "tiktok",
+    "google_business",
+    "mastodon"
+  ],
+  "example": "linkedin",
+  "type": "string"
+}
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "scheduled",
-  "publishing",
-  "published",
-  "failed",
-  "cancelled",
-  "pending_approval"
-]New value: +[
+  "scheduled",
+  "pending",
+  "processing",
+  "retry",
+  "completed",
+  "failed",
+  "canceled"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "maxLength": 512,
+  "type": "string"
+}
  4. 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."
  5. First observed

TDQS

A3.6/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), and the description adds real behavioral context on top: a 100-per-page cap, cursor-based pagination, and the important semantic that approval_status is distinct from publishing status. This goes beyond the structured annotations.

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?

Two dense sentences that are front-loaded with the resource and filters, then return-shape notes. No filler, though the semicolon-joined clauses pack several ideas together.

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?

For a 9-parameter read tool with no output schema, the description does explain the return items and the empty-array case, which is useful. However, it omits the undocumented query override, brand_id, and workspace_id parameters, so an agent lacks a complete picture of the call surface.

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 coverage is only 33%, so the description compensates partially by naming from/to, status, platform, and cursor semantics. But limit, brand_id, workspace_id, and the nested query override object are left unexplained in both schema and description, leaving real gaps.

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 (List) plus a distinct resource (workspace scheduled posts) and enumerates the main filter axes. The 'scheduled posts' scoping is concrete enough to separate it from the sibling aidelly_list_posts, though it never names that alternative explicitly.

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?

Usage is implied by the described filters and pagination rather than stated. There is no guidance on when to choose this over aidelly_list_posts or aidelly_get_scheduled_post, and no exclusions or prerequisites are given.

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