Skip to main content
Glama

aidelly

by io.github.wilzer
OverviewDiscussionsAdmin

List Posts

aidelly_list_posts
Read-onlyIdempotent

List posts with optional platform, status, and date-range filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo
fromNo
limitNo
queryNoOptional query overrides for endpoints with sparse parameter schemas.
cursorNo
statusNo
brand_idNo
platformNoSupported 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`.
workspace_idNoWorkspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / workspace_id / description
      Previous 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."New value: +"Workspace to operate in: the `id` of a workspace returned by aidelly_list_workspaces. Optional for read operations; required when creating content."
  2. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "maxLength": 512,
+  "type": "string"
+}
  3. 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."
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing behavioral beyond restating filter options found in the schema — no pagination behavior despite cursor/limit, no scoping note, no result-shape context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single front-loaded sentence with no filler. It is efficient, though the brevity is partly what leaves the tool under-specified for a 9-parameter call.

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?

For a 9-parameter, nested-object, no-output-schema tool, one sentence is not enough. Pagination via cursor/limit, the workspace_id scoping requirement, and the difference from sibling list endpoints are all unaddressed, leaving an agent to guess at correct invocation.

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 only 33%, so the description must compensate. It does map to three meaningful parameters (platform, status, and the to/from date range), but leaves brand_id, workspace_id, query, cursor, and limit unexplained in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('List posts') and enumerates the filter dimensions (platform, status, date-range). However, it does not distinguish this tool from close siblings like aidelly_list_scheduled_posts, aidelly_list_drafts, or aidelly_get_post, so an agent cannot route between them from the description alone.

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 when-to-use guidance, no prerequisites, and no named alternatives. The reader gets 'optional filters' but no signal about when to prefer this general listing over the more specific scheduled-posts or drafts listers, which is exactly the ambiguity an agent needs resolved.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources