Postemi: Social Media Scheduler

list_posts

Read-only

See the social media content calendar and posting schedule: the scheduled, draft, published and failed posts, so you can answer "what is going out on Friday?" and find a post the user wants changed, rescheduled or cancelled.

Writes nothing. Returns, per post: the postId (pass it to delete_post), the state, the publish time in BOTH UTC and the user's own local timezone, the channel's name and @handle and platform, and a short plain-text preview of the content.

The channel fields are spelled exactly as create_post spells them in its result, so a post you created earlier in this conversation can be matched to a row here.

Defaults to the next 30 days. Pass fromUtc/toUtc for any other window — call get_workspace_context first if the user gave you a local date, because these are UTC.

Magyarul: beütemezett posztok, tartalomnaptár.

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
`state`	No	Only posts in this state. QUEUE is "scheduled and waiting". Omit for all of them.
`toUtc`	No	End of the window, ISO 8601 UTC. Defaults to 30 days after the start.
`fromUtc`	No	Start of the window, ISO 8601 UTC. Defaults to now. Pass a past date to look at what has already gone out.
`integrationId`	No	Only posts for this channel (an id from list_integrations). Omit for every channel.

Output Schema

Name	Required	Description	Default
`errors`	No
`output`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly annotations, it explicitly says it writes nothing, describes the returned post fields including postId, state, UTC and local publish times, channel name/@handle/platform, and content preview. It also discloses the default time window, the UTC requirement, and how channel fields align with create_post 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?

The description is front-loaded with purpose and usage, then moves efficiently into return details and time-window guidance. Most sentences add practical value, though the closing Hungarian summary is somewhat redundant for an English-language tool definition.

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?

Given the optional parameters, output schema and read-only annotations, the description is complete enough for correct selection and invocation. It covers what the tool lists, default time window, UTC handling, key returned fields, and how postId connects to delete_post.

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 100%, so the schema already explains the four parameters well. The description adds useful workflow context by stating the default next-30-days window, emphasizing that fromUtc/toUtc are UTC, and advising get_workspace_context when the user supplies local dates.

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?

It names a specific verb/resource (list posts) and clearly scopes it to the social media content calendar and posting schedule across scheduled, draft, published and failed states. It also distinguishes itself from create_post, delete_post and get_workspace_context by describing what it returns and how postId is used.

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?

The description gives concrete use cases such as answering 'what is going out on Friday?' and locating posts to change, reschedule or cancel, and it states the default 30-day window plus the need to call get_workspace_context for local dates. It stops short of explicitly saying when to use this versus get_post or other listing/search tools, so it is strong but not fully exhaustive.

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

All Postemi: Social Media Scheduler 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.