Notipo

Update Post

update_post

Update an existing post's content or properties in Notion, then re-sync to WordPress. Only provided fields are updated.

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": {
      "postId": "<postId>"
    },
    "name": "update_post"
  }
}

Input Schema

Name	Required	Description
`body`	No	New content in markdown (replaces entire body)
`slug`	No	New URL slug
`tags`	No	New tag names
`title`	No	New title
`postId`	Yes	The post ID to update
`publish`	No	Set true to also publish after updating
`category`	No	New category name
`seoKeyword`	No	New SEO focus keyword
`seoDescription`	No	New meta description for SEO (max 160 chars)

Output Schema

Name	Required	Description	Default
`jobId`	Yes	Use get_job to poll status

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description adds non-obvious behavior: updates happen in Notion and then re-sync to WordPress. The partial-update rule ('Only provided fields are updated') is also useful and not otherwise stated.

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 description is one focused sentence with no filler. It front-loads the action and includes the most important behavioral constraint without becoming verbose.

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?

Given the full schema, output schema, and annotations, the description covers the core behavior, the cross-system sync side effect, and the partial-update rule. It could have more explicitly addressed when to use the publish parameter versus publish_post/direct_publish, but the essentials are present.

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 baseline is 3. The description adds value by clarifying partial-update semantics, which is not necessarily inferable from optional schema properties alone. It correctly avoids repeating individual parameter descriptions.

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 uses a specific verb ('Update') and clearly identifies the resource: an existing post's content or properties in Notion, followed by re-sync to WordPress. It distinguishes itself from siblings like create_post and delete_post by emphasizing 'existing post'.

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 clearly conveys that this tool is for modifying an existing post and that only provided fields are updated. It does not explicitly mention alternatives like publish_post or direct_publish, so the guidance is clear but not exhaustive.

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

All Notipo 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.