Skip to main content
Glama

aidelly

by io.github.wilzer

aidelly_create_post

Accept a post for immediate asynchronous publishing or future scheduling. HTTP 201 and ok=true mean accepted, not delivered. For immediate posts, poll aidelly_get_post and only report publication when status is completed and provider_post_id is non-null. Use aidelly_list_pinterest_boards before Pinterest posts and pass content.platform_specific.board_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoOptional body override for endpoints with sparse parameter schemas.
queryNoOptional query overrides for endpoints with sparse parameter schemas.
contentYes
brand_idNo
metadataNo
platformYesSupported 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`.
timezoneNo
account_idNoThe account / sub-account this post should target. Format depends on platform: - **facebook** — Page ID (numeric string from `/accounts`). - **instagram** — Instagram Business Account ID. - **linkedin** — connection ID for personal posts; LinkedIn organization URN for company posts. - **google_business** — GBP location resource name. Either fully-qualified `accounts/{accountId}/locations/{locationId}` or the relative `locations/{locationId}` form. Fetch with `GET /accounts` (rows where `account_type: location`). - **twitter / bluesky / threads / tiktok / youtube / pinterest / mastodon** — single-account platforms; `account_id` is optional and ignored. When omitted, posts use the workspace-level default for that platform.
scheduled_atNo
workspace_idNoWorkspace 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.
idempotency_keyYes
instagram_destinationNoInstagram-only destination. Use post for feed only, stories for Stories only, or post_stories for both feed and Stories.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate the tool is read-only (false) and not idempotent. The description adds that a 201 response means 'accepted, not delivered', which clarifies the asynchronous behavior. It does not elaborate on side effects, permissions, or error conditions beyond the annotations.

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 sentences long, each earning its place: purpose, async behavior with polling, and a key prerequisite. It is front-loaded and avoids redundancy.

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?

Given the tool's complexity (12 parameters, nested objects, no output schema), the description covers the essential behavioral context: async acceptance, polling requirement, and a platform-specific prerequisite. It omits error handling and retry logic but is sufficient for correct usage.

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 around 50%, with many parameters already well-documented in the schema. The description adds specific advice for the `platform_specific.board_id` parameter (use `aidelly_list_pinterest_boards`), which improves clarity. However, it does not significantly enrich understanding of other parameters.

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 clearly states the tool accepts a post for immediate asynchronous publishing or future scheduling. It distinguishes from siblings like `aidelly_bulk_create_posts` and `aidelly_create_scheduled_post` by covering both immediate and scheduled creation and emphasizing the async nature with polling guidance.

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 description provides explicit when-to-use and post-usage steps: polling `aidelly_get_post` for immediate posts and using `aidelly_list_pinterest_boards` before Pinterest posts. It does not mention when not to use the tool or alternatives like `aidelly_create_scheduled_post`, but the context is clear enough.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.2/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially in approvals and post updates. For example, aidelly_action_post_approval and aidelly_post_approvals_id_action both handle approval actions, while aidelly_get_approvals and aidelly_list_pending_approvals appear to serve similar listing functions. The proliferation of HTTP-route-style names with generic prefixes (get_approvals_id, patch_posts_id) further obscures distinctions.

Naming Consistency1/5

The tool set mixes clean verb_noun names (create_post, list_posts) with HTTP-method-plus-path names (get_approvals_id, patch_posts_id, post_analytics_insights). There is no consistent pattern, and 'post' as a verb collides with the content post noun, creating confusion. The inconsistent conventions make it hard to predict tool names.

Tool Count1/5

With 124 tools, this server vastly exceeds the typical MCP server scope and the calibration threshold (50+ is extreme). Even for a comprehensive platform API, such a large surface overwhelms agents and makes selection impractical. The count is a severe mismatch for a usable MCP tool set.

Completeness4/5

The tool surface is remarkably comprehensive, covering CRUD for posts, drafts, scheduled posts, tasks, reports, webhooks, workspaces, e-commerce stores, and many more. Advanced features like approvals, repurpose jobs, and content automations are also represented. Minor gaps exist (e.g., no explicit delete for regular posts, only cancel), but the domain is well covered overall.

Resources