Skip to main content
Glama

Postproxy

by dev.postproxy
OverviewDiscussionsAdmin

post_update

Destructive

Update an existing post. Only drafts or scheduled posts (more than 5 min before publish) can be updated. Only send fields you want to change — omitted fields are left unchanged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftNoSet or unset draft status
mediaNoReplace all media (array of media URLs). Full replace — send empty array to remove all. Omit to keep existing.
threadNoReplace all thread children (full replace). Send empty array to remove all. Omit to keep existing.
contentNoUpdated text content
post_idYesPost ID to update
profilesNoReplace all profiles (array of profile IDs or platform names). Full replace — omit to keep existing.
queue_idNoQueue ID to assign the post to
scheduleNoUpdated ISO 8601 scheduled time
platformsNoPlatform-specific parameters (merged with existing). Same structure as post.publish.
queue_priorityNoQueue priority

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already show destructiveHint=true, but description adds valuable context about partial updates and post status constraints. No contradiction.

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?

Two sentences, no fluff, critical information front-loaded. Every sentence adds value.

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?

Covers core behavior and constraints. No output schema, but parameters are well-documented in schema. Could mention error cases or return format, but not required for a simple update tool.

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 baseline is 3. Description adds general partial-update guidance but no param-specific detail beyond 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?

Description clearly states 'Update an existing post' with specific constraints. Distinguishes from siblings like post_delete and post_publish.

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 states when to use (only drafts or scheduled posts more than 5 min before publish) and provides update strategy ('only send fields you want to change').

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

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