List webhook subscriptions for post lifecycle events.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Optional query overrides for endpoints with sparse parameter schemas. | |
| brand_id | No | ||
| workspace_id | No | 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. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds minimal behavioral context with 'for post lifecycle events' but does not disclose traits like return format, pagination, or authentication needs beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Exceptionally concise single sentence of 8 words, no filler. Front-loaded with the key action and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only list tool with no output schema, the description covers the basic purpose but lacks details on expected output format, filtering behavior, or limitations. Adequate but not thorough.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema_description_coverage is 67%, but the description does not elaborate on any parameters. It adds no additional meaning beyond the schema's brief descriptions of 'query' and 'workspace_id', leaving 'brand_id' undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states action and resource: 'List webhook subscriptions for post lifecycle events.' It specifies the domain of subscriptions and the lifecycle events, distinguishing it from sibling tools like 'aidelly_list_webhook_deliveries' which list deliveries instead.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as 'aidelly_list_webhook_deliveries' or 'aidelly_create_webhook'. The description only states what it does, leaving the agent to infer context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
