Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

Blog: Publish post

blog_publish_post
Destructive

Publish a blog post on its site now, or schedule it for a future moment ('publish_at', ISO-8601 with timezone). The post becomes visible to site visitors at that moment. Reversible from the cabinet (unpublish). Runs propose→confirm. CONFIRMATION: this tool is PROPOSED, never performed directly. You get status='confirmation_required' with an action_id and a plan_token, and the write happens only after confirm_action.

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": {
      "post_id": "<post_id>"
    },
    "name": "blog_publish_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
publish_atNoISO-8601; omit to publish now.

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?

Beyond the annotations, the description discloses the key workflow: the tool only proposes the action, returns status='confirmation_required' with action_id and plan_token, and performs the write only after confirm_action. It also adds important behavioral context about visitor visibility and reversibility via unpublish.

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 appropriately sized and front-loads the core publish-or-schedule behavior. The confirmation workflow is clearly stated, though 'Runs propose→confirm' and the longer CONFIRMATION segment partially repeat the same idea.

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?

For a write tool with a propose→confirm safety workflow, the description covers the most important behavior an agent needs: scheduling semantics, visibility, reversibility, and confirmation mechanics. It is somewhat less complete on parameter meaning for 'post_id' and on error or edge-case behavior.

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?

The schema documents 'publish_at' as ISO-8601 and optional, but not 'post_id'. The description adds that 'publish_at' includes timezone and controls immediate versus scheduled publishing, but it does not explain 'post_id', leaving the 50% schema coverage gap only partially compensated.

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?

The description states a specific verb and resource: publish a blog post on its site. It clearly distinguishes publishing now from scheduling for a future moment via 'publish_at'.

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?

It explains the primary usage choice: publish now, or schedule later by supplying 'publish_at'. It also explains that the action is reversible via unpublish and that it requires a propose→confirm flow, though it does not explicitly compare against siblings such as blog_update_post or blog_create_draft.

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

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