Skip to main content
Glama

aidelly

by io.github.wilzer

aidelly_create_task

Create a new task in the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoOptional body override for endpoints with sparse parameter schemas.
queryNoOptional query overrides for endpoints with sparse parameter schemas.
titleYesTask title.
due_atNoISO 8601 due date/time.
statusNoTask status (default "todo").
brand_idNo
priorityNoTask priority (default "normal").
descriptionNoTask description.
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.
linked_idea_idNoUUID of linked idea (mutually exclusive with linked_post_id).
linked_post_idNoUUID of linked post (mutually exclusive with linked_idea_id).
idempotency_keyYes
assignee_user_idNoUUID of assignee (must be an active workspace member).

Schema Changelog

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

  1. Added

TDQS

B3/5.0
Behavior2/5

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

Annotations indicate a mutable operation (readOnlyHint=false), but the description does not elaborate on behavioral traits such as idempotency, conflict handling, required permissions, or side effects. The description adds no value 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but overly minimal. It could include more useful information (e.g., about idempotency or required workspace_id) without becoming verbose.

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?

Given the tool's complexity (13 parameters, no output schema), the description is incomplete. It lacks details on return value, idempotency key purpose, and the need for workspace_id. This may hinder correct invocation by an AI agent.

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 high (85%), so the parameters are well-documented in the schema. However, the description does not add any additional meaning or usage context for parameters. Baseline 3 is appropriate.

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 'Create a new task in the workspace.' uses a specific verb and resource, clearly distinguishing it from sibling tools like aidelly_update_task, aidelly_delete_task, and aidelly_create_idea.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. While the schema includes a note on workspace_id, the description itself offers no 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