Skip to main content
Glama

Update post

update_content_post
DestructiveIdempotent

Change a draft or scheduled post: working title, main text, hashtags, format, or its channels and their own texts (sending channels replaces the whole set). Fields you omit stay as they are; images cannot be changed here. Refused for a published post — a post already live on a network cannot be changed from Obriym; create a new one instead. Refused while the post is being published. Repeating the same call changes nothing further. Echoes the workspace.

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": {
      "id": "<id>"
    },
    "name": "update_content_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe publication id returned by create_content_post or list_content_posts.
textNoReplaces the main text.
titleNoAn internal working title shown in Obriym's Publications list, e.g. "Monday — new arrivals". Never published.
formatNopost = a regular feed post; story = an Instagram/Facebook story, which needs an image. Defaults to post.
channelsNoReplaces the post's channels and their texts. Omit to keep them as they are.
hashtagsNoReplaces the hashtags, without the "#" sign. Omit to keep them; [] removes them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / channels / items / properties / channel / description
      Previous value: -"A social channel: telegram (the bound Telegram channel), instagram, facebook (the Facebook page), linkedin or threads. Use only channels list_content_channels reports as ready."New value: +"A social channel: telegram (the bound Telegram channel), instagram, facebook (the Facebook page), linkedin, threads or viber (the connected Viber channel). Use only channels list_content_channels reports as ready."
    • changedInput schema / properties / channels / items / properties / channel / enum
      Previous value: -[
      -  "instagram",
      -  "facebook",
      -  "telegram",
      -  "linkedin",
      -  "threads"
      -]New value: +[
      +  "instagram",
      +  "facebook",
      +  "telegram",
      +  "linkedin",
      +  "threads",
      +  "viber"
      +]
    • changedInput schema / properties / channels / maxItems
      Previous value: -5New value: +6
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: omitting fields preserves them (patch semantics), images cannot be changed, published/publishing posts are refused, repeated calls are no-ops, and the workspace is echoed back. This is unusually rich behavioral disclosure that materially changes how an agent should call it.

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?

Front-loads the editable fields, then the patch/idempotency semantics, then the refusal conditions. Dense but every clause conveys a distinct, actionable constraint.

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?

A mutation tool with no output schema, yet the description covers state semantics, refusal conditions, and the return ('echoes the workspace'). Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the baseline is 3. The description adds a little beyond the schema by clarifying that sending channels replaces the whole set and that omitted fields are preserved, but the per-parameter details already live in the schema.

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?

States a specific verb (change) and resource (a draft or scheduled post) plus the exact editable fields, so an agent can distinguish it from create_content_post, delete_content_post, and publish_content_post without opening the schema.

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

Usage Guidelines5/5

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

Explicitly scopes usage to drafts/scheduled posts, names the when-not conditions (published post → create a new one instead; refused while publishing), and routes the agent to the create path as the alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources