Skip to main content
Glama

aidelly

by io.github.wilzer

aidelly_delete_draft

DestructiveIdempotent

Delete a draft by ID. Drafts are work-in-progress content that never publish. Existing API keys need the new drafts:write scope added to gain draft access; no implicit grant occurs.

Input Schema

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

Schema Changelog

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

  1. Changed2 schema fields changed
    • removedInput schema / properties / id / description
      Removed value: -"Draft ID."
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "idempotency_key"
-]New value: +[
+  "idempotency_key",
+  "id"
+]
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

The description discloses a critical behavioral trait beyond the annotations: existing API keys need the `drafts:write` scope and no implicit grant occurs. This adds meaningful context about auth requirements, which is not present in the annotations. It also clarifies the nature of drafts, adding value beyond the destructiveHint.

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 highly concise, with three sentences that each add value: clear purpose, draft context, and auth warning. No redundant or filler content exists, and the most critical information is front-loaded.

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?

While the description covers purpose, draft nature, and access scope, it leaves gaps for a deletion tool with 5 parameters and no output schema. It does not clarify whether workspace_id is required for delete operations, nor does it explain the role of the required idempotency_key. The query parameter semantics are also vague, making the tool less than fully transparent.

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?

With schema description coverage at only 40%, the description should compensate for undocumented parameters. It only mentions 'by ID' and does not explain idempotency_key, brand_id, or the workspace_id requirements. The schema itself lacks descriptions for these required/optional fields, so the agent receives insufficient parameter guidance.

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 starts with 'Delete a draft by ID,' which is a specific verb+resource statement that clearly distinguishes this tool from sibling draft operations like create, get, update, and list. It also clarifies the nature of drafts, reinforcing the purpose.

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 clear context that drafts are work-in-progress content that never publish, implying this tool is for deleting unpublished drafts rather than published content. However, it does not explicitly name alternative tools or exclusions, so it falls short of full usage guidance.

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