Skip to main content
Glama

uplika

by com.uplika
OverviewDiscussionsAdmin

List posts published here

list_posts
Read-only

Recent publishes made through us and the per-target status of each, scheduled and draft posts included (their status says so and scheduledAt says when). Newest first, 20 by default. Pass limit for more or fewer, up to 100. hasMore means the list was cut short; pass the returned nextBefore as before to keep going. To answer "what is scheduled this week", pass status scheduled with since and until and sort scheduled. Posts that already existed on the channel are not here. Use list_channel_posts for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoscheduled orders by the post's date ascending (soonest first) and drops paging. Omit for newest first.
limitNo1-100, defaults to 20
sinceNoYYYY-MM-DD or ISO 8601. Only posts dated at or after this. A scheduled post is dated by its scheduledAt, a sent post by when it was created.
untilNoYYYY-MM-DD or ISO 8601. Only posts dated at or before this (a date means the whole day).
beforeNoA publish id from a previous page's nextBefore. Returns the ones older than it.
statusNoNarrow to one or more statuses, comma separated: scheduled, draft, publishing, published, partial, failed or cancelled. Omit for everything.
workspaceIdNoWhich workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / since
      Added value: +{
+  "description": "YYYY-MM-DD or ISO 8601. Only posts dated at or after this. A scheduled post is dated by its scheduledAt, a sent post by when it was created.",
+  "type": "string"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "scheduled orders by the post's date ascending (soonest first) and drops paging. Omit for newest first.",
+  "enum": [
+    "scheduled"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / status / description
      Previous value: -"Narrow to one status: publishing, published, partial, failed or cancelled. Omit for everything."New value: +"Narrow to one or more statuses, comma separated: scheduled, draft, publishing, published, partial, failed or cancelled. Omit for everything."
    • addedInput schema / properties / until
      Added value: +{
+  "description": "YYYY-MM-DD or ISO 8601. Only posts dated at or before this (a date means the whole day).",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "description": "Which workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"Narrow to one status: publishing, published, failed or cancelled. Omit for everything."New value: +"Narrow to one status: publishing, published, partial, failed or cancelled. Omit for everything."
  4. Changed1 schema field changed
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Narrow to one status: publishing, published, failed or cancelled. Omit for everything.",
+  "type": "string"
+}
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: inclusion of scheduled/draft posts, paging semantics (hasMore, nextBefore, limit cap of 100), ordering ('newest first'), and the exclusion of pre-existing channel posts. This is rich, non-obvious behavior.

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 a dense but well-ordered paragraph: scope, default behavior, paging, usage example, exclusions, and sibling alternative. Every sentence carries new information and is front-loaded with the core purpose. No fluff or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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 what is returned, ordering, pagination, filtering, defaults, and the boundary vs. list_channel_posts. With rich parameter schemas and annotations, nothing an agent needs to invoke it correctly is missing.

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 100%, so the baseline is 3. The description reinforces the paging parameter interaction ('pass the returned nextBefore as before') and gives a filter example, but it largely restates what the schema already documents (limit default, sort behavior, since/until semantics). It adds marginal value over the schema, so 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 states a specific verb and resource ('list posts published through us'), enumerates what the list includes (recent publishes, scheduled, drafts), and explicitly contrasts with list_channel_posts. An agent can immediately distinguish this from the sibling tool without reading schemas.

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

Usage Guidelines5/5

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

It gives direct when-to-use guidance: 'Posts that already existed on the channel are not here. Use list_channel_posts for those.' It also provides a concrete use-case pattern ('To answer "what is scheduled this week", pass status scheduled with since and until and sort scheduled.'), which fully routes the agent to the right tool and parameter combination.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All uplika 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