Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Get scheduled post

get_scheduled_post
Read-onlyIdempotent

Get one post by its numeric id: content, media, each platform target with its own status, error details, and posting history. For a blog post it also returns a JSON export (rendered HTML body, slug, excerpt, author, tags, cover image) that can be used to display the published post on another site. 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>",
      "id": "<id>"
    },
    "name": "get_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe numeric ID of the scheduled post.
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.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the description's main value is in describing what is returned: platform-specific statuses, error details, posting history, and a blog JSON export. That is meaningful behavioral context beyond the annotations, though not-found and permission behavior are not covered.

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?

The response content is front-loaded in the first sentence, with the blog-export detail and read-only note following efficiently. Every sentence adds useful selection or return-value context without waste.

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 appropriately explains the returned post structure and the special blog JSON export. It is nearly complete for a read-only single-resource getter, though it omits error behavior for invalid ids or missing workspace access.

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 both parameters are documented in the schema, including workspace_key with a pointer to list_workspaces. The description reinforces that id is numeric but adds little parameter meaning beyond the schema.

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: retrieve one post by numeric id. It also scopes the return to content, media, per-platform status, errors, posting history, and blog JSON export, which clearly distinguishes a single-post fetch from list-style siblings, though it does not name an alternative tool.

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

Usage Guidelines2/5

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

It implies the tool is used when a numeric post id is known, but gives no explicit guidance on when to use it instead of list_scheduled_posts, get_generated_post, or edit_scheduled_post. There are no exclusions or alternative-selection rules.

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