SuperPost

Search posts

list_posts

Read-onlyIdempotent

Lists or searches saved posts with bounded pagination. The external OAuth Read SuperPost data disclosure includes saved post text with unknown source provenance; known Google-derived post text is available only when the current, versioned Google post-content disclosure was accepted for this connection. Direct Google source files, images, video bytes, and transcription remain separately restricted by provider permissions and source grants. Filter by editorial readiness (raw, in_progress, needs_review, approved, archived), calendar placement (unscheduled, planned, scheduled, publishing, published, failed), overdue=true for planned slots whose planned time has passed, or approvedVideoMontage=true for a video currently attached to its channel variant whose exact Montage has a separate creator approval marker. A render marked ready_for_review alone does not satisfy video approval; Post and variant approval are separate. Set includeVideoApprovalDiagnostics=true to return bounded, content-free reason codes keyed by Post ID/revision for provenance-safe posts inspected on that page; restricted source-derived posts are never diagnosed or exposed. Readiness and placement are separate dimensions. References include the exact Post ID and revision needed for a later archive or schedule review proposal. Full shared text and platform versions are not included in this search result.

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

Name	Required	Description
`limit`	No
`query`	No
`cursor`	No
`overdue`	No	Filter by planned calendar slots whose planned time has already passed. This status is separate from post readiness.
`placement`	No
`readiness`	No
`approvedVideoMontage`	No	Return only posts whose currently attached video matches a completed Montage with a separate creator approval marker. Post/variant approval is a separate state.
`includeVideoApprovalDiagnostics`	No	Return content-free reason codes keyed by safe Post IDs/revisions for this page. Source-provenance-restricted posts are withheld before inspection; no post text, source details, file names, media bytes, or Montage IDs are included.

Output Schema

Name	Required	Description	Default
`items`	Yes
`nextCursor`	No
`withheldCount`	Yes
`videoApprovalDiagnostics`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description earns credit for adding context annotations cannot carry: the OAuth disclosure boundaries, that restricted source-derived posts are withheld entirely, that diagnostics are content-free reason codes, and that full shared text and platform versions are excluded from results. The caveat that a ready_for_review render does not satisfy video approval is a genuinely useful behavioral distinction. It loses a point only because the permission/provenance prose is dense enough to obscure the operational facts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the body runs long and several sentences are heavy compliance prose ('The external OAuth Read SuperPost data disclosure includes saved post text with unknown source provenance...') that an agent must parse to reach the actionable filter rules. The filter guidance could be restructured into a compact list rather than embedded mid-paragraph.

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 not be described, and the description still usefully states what is deliberately absent from results (full shared text, platform versions) and that references carry Post ID plus revision. For an eight-parameter read tool with disclosure constraints, this is close to complete; only explicit alternative routing is missing.

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 description coverage is only 38%, so the description has to compensate and largely does: it enumerates all five readiness values and all six placement values, clarifies that readiness and placement are independent axes, and explains both const-true flags. It leaves `limit`, `query`, and `cursor` entirely to the schema, which is acceptable for conventional pagination and search arguments but is the reason this is not a 5.

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 opening sentence names a specific verb and resource ('Lists or searches saved posts') plus a scoping trait ('bounded pagination'), which is enough to separate it from search_sources, list_ideas, and list_publications. It stops short of naming any sibling or stating explicitly why an agent would pick this over those adjacent listing tools.

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 conveyed indirectly through filter semantics: readiness vs placement are declared separate dimensions, `overdue=true` is scoped to planned slots, and `approvedVideoMontage=true` is scoped to a currently attached approved video. There is no explicit when-to-use / when-not-to-use guidance and no routing to alternatives such as list_publications or preview_schedule_edit for the downstream actions it hints at.

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

All SuperPost tools Inspect

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

Need Help?