Skip to main content
Glama

uplika

by com.uplika

List posts published here

list_posts
Read-only

Recent publishes made through us and the per-target status of each. 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. Posts that already existed on the channel are not here. Use list_channel_posts for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo1-100, defaults to 20
beforeNoA publish id from a previous page's nextBefore. Returns the ones older than it.
statusNoNarrow to one status: 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.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description reveals key behavior: newest-first ordering, a default limit of 20 with a max of 100, pagination semantics (hasMore and nextBefore), and the exclusion of pre-existing channel posts. This gives the agent a strong mental model of how the tool behaves.

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 four concise sentences, front-loaded with the main purpose and followed by necessary behavioral details. Every sentence adds value with 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?

The tool has 4 parameters and no output schema, but the description covers the core behavior, pagination, limits, scope, and an alternative. It provides enough context to invoke the tool correctly without needing additional explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the limit default and range, and how to use before with the returned nextBefore for pagination. It does not re-explain workspaceId, but the schema already covers that well.

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 the tool lists recent publishes made through the service, with per-target status, and explicitly distinguishes itself from list_channel_posts by noting pre-existing channel posts are excluded. This gives a specific verb, resource, and scope while differentiating from a sibling tool.

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?

The description provides explicit usage guidance: when to use (for publishes made through the service), how to paginate using hasMore and nextBefore, and an explicit alternative (use list_channel_posts for pre-existing channel posts). It covers both when and when-not more clearly than most tools.

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

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, and descriptions actively steer usage (e.g., get_post vs open_post, list_posts vs list_channel_posts). A few pairs like list_accounts vs select_channels or get_post vs open_post still require careful reading to pick the right one, but the overlap is manageable.

Naming Consistency4/5

The dominant pattern is verb_noun (delete_post, get_insights, list_accounts, select_channels), which is consistent and predictable. A few bare-verb names like publish and reply, plus the media_* prefixed tools, break the strict pattern but still feel coherent within their subdomains.

Tool Count4/5

20 tools is on the heavier side, but the breadth is justified by the server's scope: publishing, media upload workflows, reply threads, insights, quotas, and account selection. Each tool has a real job, though the four post-retrieval variants and five media tools could feel redundant at a glance.

Completeness4/5

The core lifecycle is well covered: publish, reply, delete, retry, retrieve, list, and get insights, plus multi-step media handling. Minor gaps exist, such as no general post editing, no delete-reply action beyond hiding, and limited scheduling outside YouTube, but these are not critical for the stated purpose.

Resources