Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

List scheduled posts

list_scheduled_posts
Read-onlyIdempotent

List a workspace's posts on the content calendar. Each entry has the post id, status, platform, scheduled time, and a short content preview.

Optional filters: status (scheduled, processing, published, failed, draft, retrying, or all; default scheduled), type (blog, image, video, or all; default all), from and to (ISO 8601 datetimes), and limit (1-100, default 20). For example, status "published" with type "blog" lists published blog posts. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_key": "<workspace_key>"
    },
    "name": "list_scheduled_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO 8601 datetime — only return posts at or before this time.
fromNoISO 8601 datetime — only return posts at or after this time.
typeNoFilter by content type: 'blog' (articles), 'image' (designs), 'video'. Defaults to 'all'.
limitNoMax posts to return (1–100). Defaults to 20.
statusNoFilter by post status. Defaults to 'scheduled'.
workspace_keyYesKey of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: the default status is 'scheduled', the default type is 'all', and each returned entry contains specific fields. It does not cover ordering or rate limits, but the added default-filtering behavior is meaningful.

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 the core purpose and then organized by return fields and filters. It is mostly efficient, though it repeats several schema details and the annotation-backed 'Read-only' fact, which slightly reduces conciseness.

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?

There is no output schema, so the description usefully explains the return entry shape. Together with the complete input schema and rich annotations, it gives enough information to select and invoke the tool correctly without needing external context.

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 description coverage is 100%, and the schema already documents all six parameters, including enums and defaults. The description mirrors those defaults and adds a small example of combining status and type, but it does not add much semantic detail beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: list a workspace's posts on the content calendar. It also clarifies that entries include id, status, platform, scheduled time, and preview. It does not explicitly distinguish itself from siblings like get_scheduled_post, so it is clear but not fully sibling-differentiated.

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?

The description documents filters and gives an example combination, which implies how to use the tool. However, it does not explicitly say when to use this instead of get_scheduled_post, schedule_posts, or edit_scheduled_post, and it gives no exclusions or when-not guidance.

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

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