publish_postPublish a draft post to WordPress (make it live).
| Name | Required | Description | Default |
|---|---|---|---|
| postId | Yes | The post ID to publish |
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | Yes | Use get_job to poll status |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is not read-only and not destructive. The description adds the key behavioral detail that the post transitions from draft to live, which is useful. It does not mention prerequisites, failure conditions, or side effects, but for this simple operation the added context is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that states the action and outcome with no filler. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one fully documented parameter, annotations, and an output schema present, the description is sufficient for an agent to select and invoke this tool correctly. No critical contextual information is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the sole parameter, postId, is already documented as 'The post ID to publish'. The description adds the draft-to-live context but does not meaningfully extend the parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the action ('Publish'), the resource ('a draft post to WordPress'), and the effect ('make it live'). It distinguishes the tool from create_post and update_post, though it does not explicitly differentiate it from the sibling direct_publish.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool instead of alternatives. In particular, the presence of direct_publish as a sibling makes this a meaningful gap, since an agent cannot tell which publishing workflow to choose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target clearly distinct resources and actions, separating creation, updates, deletions, list/get operations, and job monitoring. The main ambiguity is between direct_publish and publish_post, since both involve publishing, though their descriptions clarify creation vs. making a draft live.
The majority of tools follow a clear verb_noun pattern: create_post, get_post, list_posts, update_post, delete_post, publish_post, list_categories, list_tags. The exceptions are direct_publish and sync_now, which deviate from the pattern but remain understandable.
13 tools is well-scoped for a blogging and sync workflow covering posts, publishing, jobs, categories, tags, and settings. Each tool addresses a distinct part of the pipeline without redundancy or excessive granularity.
The surface covers the core post lifecycle, publishing jobs, sync triggers, WordPress metadata, and settings. The only notable gap is that direct_publish creates a WordPress post outside of Notion, while update_post explicitly syncs back from Notion, so updating a direct-published post may not be covered.