Skip to main content
Glama
Sign In

Octopost

by ink.octopost
OverviewDiscussionsAdmin

List posts

list_posts
Read-onlyIdempotent

List posts, newest first: content preview, platforms, status, scheduled time and each network's link. Filter with status. Results are paged: when next_cursor is set, call again with cursor = next_cursor for the next page. Call get_post for one post's full details.

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
limitNoPosts per page (default 10, max 50).
cursorNonext_cursor from the previous list_posts call, to get the next page. Keep the same status filter.
statusNoFilter by status. "queued" = in the active queue, "pending" = waiting for human approval, "partial" = live on some networks only. Omit for all posts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds behavior beyond them: deterministic newest-first ordering, the paginated loop driven by next_cursor, and an enumeration of what each result carries. No rate limits or empty-result behavior, but the added context is substantive.

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?

Four short sentences, front-loaded with purpose and return shape before the filtering and pagination mechanics. Every clause carries actionable information; nothing restates the name or wastes tokens.

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 no output schema, the description correctly compensates by listing the returned fields, and it fully covers pagination and filtering for a simple three-parameter list tool. Minor gaps remain around total counts or behavior on empty results, but an agent has everything needed to call and iterate it correctly.

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 limit, cursor and status are already documented, including the enum meanings. The description nonetheless adds procedural meaning the schema only implies: that cursor must be fed back verbatim from next_cursor and that the status filter must be kept constant across pages. That is genuine value beyond the schema.

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?

States a specific verb and resource ("List posts") plus the ordering ("newest first") and the exact fields returned (preview, platforms, status, scheduled time, per-network link). It also explicitly routes single-post retrieval to get_post, so an agent can separate it from that sibling without opening either schema.

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

Usage Guidelines4/5

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

Gives concrete usage instructions: filter with status, and a precise pagination recipe ("when next_cursor is set, call again with cursor = next_cursor"). It names get_post as the alternative for full detail. It lacks an explicit when-not case (e.g. no per-account or date filtering available), so it stops short of full routing guidance.

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

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