Skip to main content
Glama

aidelly

by io.github.wilzer

aidelly_get_post

Read-onlyIdempotent

Get one post by its UUID. Delivery is confirmed only when status is completed and provider_post_id is non-null. A failed status includes error_code and error.

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.

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

A3.8/5.0
Behavior4/5

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

The description adds behavioral context beyond the readOnlyHint annotation: it clarifies how delivery confirmation works (status completed and provider_post_id non-null) and that failed status includes error_code and error. This provides valuable nuance without contradicting 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 extremely concise with two sentences. The first sentence delivers the core purpose immediately, and the second adds essential behavioral details without waste. Ideal front-loading for AI agent processing.

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?

The description provides key behavioral details (delivery confirmation, failure) but lacks a full return value description. Without an output schema, the agent may need more context on the response structure. The annotations are good, but the description could be more complete for a tool with 4 parameters and no output schema.

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 coverage is 50%, and the description does not add meaning to any parameters beyond what the schema already provides. The id and brand_id parameters lack schema descriptions, and the description does not explain the query or workspace_id parameters beyond the schema's own guidance. The description fails to compensate for the low 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 clearly states 'Get one post by its UUID' with a specific verb and resource. It adds extra context about delivery confirmation and failure status, distinguishing it from list tools like aidelly_list_posts. The title 'Get Post' reinforces 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 Guidelines3/5

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

The description implies usage when a post UUID is available, but does not explicitly guide when to use this tool versus alternatives like aidelly_list_posts or other get tools. No when-not or exclusion criteria are provided.

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