Skip to main content
Glama
Sign In

aidelly

by io.github.wilzer
OverviewDiscussionsAdmin

Update Scheduled Post

aidelly_update_scheduled_post
Destructive

Update the caption, schedule, or recycle plan of a scheduled post. Overwrites the supplied fields; a new time changes when the post publishes. Retry-safe: a repeat call with the same idempotency_key returns the original result.

Input Schema

NameRequiredDescriptionDefault
idYes
bodyNoOptional body override for endpoints with sparse parameter schemas.
queryNoOptional query overrides for endpoints with sparse parameter schemas.
payloadNoReplacement post content. `payload.media` accepts URL objects, objects with `media_id`, or bare media-library UUID strings owned by the selected workspace. Send `media[].title` again with replacement media to keep a LinkedIn document title.
recycleNo
brand_idNo
timezoneNo
scheduled_atNo
workspace_idNoWorkspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content.
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / payload / description
      Previous value: -"Replacement post content. `payload.media` accepts URL objects, objects with `media_id`, or bare media-library UUID strings owned by the selected workspace."New value: +"Replacement post content. `payload.media` accepts URL objects, objects with `media_id`, or bare media-library UUID strings owned by the selected workspace. Send `media[].title` again with replacement media to keep a LinkedIn document title."
    • addedInput schema / properties / payload / properties
      Added value: +{
+  "media": {
+    "description": "Attachments. Each item is a media-library UUID string, a media URL string, or an object.",
+    "items": {
+      "anyOf": [
+        {
+          "description": "Media-library UUID owned by the workspace, or a publishable media URL.",
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "properties": {
+            "media_id": {
+              "type": "string"
+            },
+            "title": {
+              "description": "Title LinkedIn shows on a document (PDF carousel) post, trimmed, up to 200 characters. Without one, LinkedIn shows the uploaded file name. Also sent as the title of a LinkedIn video; other platforms ignore it.",
+              "maxLength": 200,
+              "type": "string"
+            },
+            "type": {
+              "enum": [
+                "image",
+                "video",
+                "gif",
+                "document"
+              ],
+              "type": "string"
+            },
+            "url": {
+              "format": "uri",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        }
+      ]
+    },
+    "maxItems": 10,
+    "type": "array"
+  }
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / idempotency_key / example
      Added value: +"order-123:create-post:v1"
    • addedInput schema / properties / idempotency_key / maxLength
      Added value: +255
    • addedInput schema / properties / idempotency_key / minLength
      Added value: +1
    • addedInput schema / properties / idempotency_key / pattern
      Added value: +"^[\\x21-\\x7E]{1,255}$"
  3. 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."
  4. Changed1 schema field changed
    • addedInput schema / properties / payload / description
      Added value: +"Replacement post content. `payload.media` accepts URL objects, objects with `media_id`, or bare media-library UUID strings owned by the selected workspace."
  5. 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."
  6. First observed

TDQS

B3.1/5.0
Behavior1/5

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

The annotations declare idempotentHint=false, while the description promises retry safety via idempotency_key and says a repeat call returns the original result. That directly conflicts with the non-idempotent annotation, so this dimension is scored 1 even though the overwrite/destructive note is consistent with destructiveHint=true.

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?

The description is three front-loaded sentences with no filler. Each sentence carries useful information: update scope, overwrite semantics, and retry behavior.

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

Completeness2/5

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

For a destructive, open-world mutation with nested parameters and no output schema, the description covers overwrite and retry behavior but omits prerequisites, workspace scoping, media replacement semantics, and normal response behavior. Significant gaps remain for a 10-parameter tool.

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 40% across 10 parameters. The description mentions caption, schedule, recycle plan, and idempotency behavior, but leaves workspace_id, brand_id, timezone, and much of payload/media handling undocumented in prose, so it does not compensate for the low schema coverage.

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 names a specific verb and resource: update a scheduled post, specifically its caption, schedule, or recycle plan. This clearly distinguishes it from sibling tools such as create_scheduled_post, cancel_scheduled_post, and get_scheduled_post.

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?

It implies the tool is for editing an existing scheduled post and gives retry guidance, but it does not explicitly say when to use this versus create_scheduled_post, update_post, or cancel_scheduled_post. No prerequisites or exclusions are stated, so usage is inferable but not fully guided.

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