Skip to main content
Glama

List posts

list_posts
Read-onlyIdempotent

Your posts, in pages: limit (default 20, up to 100) and cursor (next_cursor from the previous page). status 'upcoming' (scheduled, soonest first) or 'history' (published, failed, cancelled; newest first). Filter by video_id or profile_id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page (default 20, up to 100)
cursorNonext_cursor from the previous page; omit for the first page
statusNo
video_idNo
profile_idNo

Output Schema

NameRequiredDescriptionDefault
postsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds behavior the annotations do not: default and maximum page size, cursor-based paging, and sort order per status ('soonest first' vs 'newest first'), which materially affects how an agent interprets results.

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?

Three short clauses with zero filler, and the pagination mechanics are front-loaded. The telegraphic, fragment-heavy style trades a little readability for density but never buries the key information.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description covers paging and ordering adequately for a five-parameter, all-optional list tool. The remaining gap is filter composition (AND/OR semantics between video_id and profile_id) and any scope or permission notes.

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 coverage is only 40%, so the description must carry weight for status, video_id, and profile_id. It does well on status, explaining the enum meanings and ordering, but video_id and profile_id are only mentioned as filters with no indication of what relationship is matched or whether the two combine. The limit and cursor text largely restates the schema.

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 opens with 'Your posts, in pages', which conveys the resource and the paginated-list nature, and the filter/paging vocabulary makes it distinguishable from single-item siblings like get_post. It never states the verb explicitly, relying on the title and schema to confirm this is a read-only list operation.

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?

Usage is implied through the status semantics: 'upcoming' for scheduled posts, 'history' for published/failed/cancelled. That is genuinely useful selection guidance, but there is no explicit when-to-use versus when-not-to-use, and no sibling such as get_post or list_videos is named as an alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.