Skip to main content
Glama

Eurekuh

List posts

list_posts
Read-onlyIdempotent

The organization's posts, newest first. Filter by status to see what is waiting: "draft", "scheduled", "pending_approval" (waiting for someone who can publish to approve it in the app), "awaiting_plan" (held until the organization starts its trial or a plan), "queued", "processing", "complete", "failed" or "removed" (published, then deleted on the network). Each post's media holds mediaId values create_post accepts, so a post can be scheduled again without re-uploading. firstComment shows when the first comment goes out and whether it has (waiting, posted, failed + why). Returns { posts, nextCursor }: while nextCursor is not null, pass it back as cursor with the same filters for the next page.

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
sortNo"createdAt" newest first (default), "scheduledAt" soonest first, "scheduledAtDesc" latest first. Posts with no time go last.
limitNoHow many per page, up to 200. Default 50.
cursorNonextCursor from the previous page.
statusNoOnly posts in this status.
platformNoOnly posts to this network, e.g. "tiktok".
accountIdNoOnly posts to this account (an id from list_accounts).
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.
scheduledAfterNoOnly posts scheduled at or after this ISO time.
scheduledBeforeNoOnly posts scheduled at or before this ISO time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description goes well beyond them: it discloses the return shape `{ posts, nextCursor }`, the pagination loop, that `media` carries mediaIds reusable by create_post, and that `firstComment` reports both send time and outcome (waiting/posted/failed + why). This is exactly the cross-tool behavioral context annotations cannot express.

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?

Front-loaded with the resource and ordering, then filters, then return/pagination contract — a logical order with no filler sentences. It is dense with parentheticals, which costs some scanability, but nearly every clause carries information an agent needs.

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?

With nine optional parameters and no output schema, the description still supplies the return shape, the pagination contract, and the meaning of the non-obvious fields (`media`, `firstComment`). An agent can call this correctly and know how to iterate pages without any other source.

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, but the description adds real meaning by defining each `status` value's semantics and by reinforcing the sort default and cursor reuse rule. It doesn't elaborate on the date-range or account filters, which the schema already handles.

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?

States a specific verb and resource scoped to the organization ("The organization's posts, newest first"), which implicitly separates it from network-wide listings. It never names a sibling alternative such as list_network_posts, so differentiation is left to inference rather than stated.

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 guidance on using the status filter to find posts "waiting" for action and explains what each waiting state means operationally (e.g. pending_approval waits on a publisher, awaiting_plan is held until trial/plan). It also instructs how to paginate. It does not state when to prefer a different listing tool, so it falls short of explicit alternatives.

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.

Resources