Skip to main content
Glama
Sign In

Posthell

by io.github.Rohan27s
OverviewDiscussionsAdmin

Edit a post's text or time

edit_post

Change the caption (body), a network's own caption (overrides), and/or the suggested time of a DRAFT. Scheduled posts can only be moved with reschedule_post: changing the text of a post that is already scheduled needs a key the user has allowed to publish. Get the id from list_posts.

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": "edit_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoNew caption for every network that has no caption of its own
postIdYesThe post id from list_posts
overridesNoA caption of its own for a network, used instead of body there. For YouTube this is the video description.
scheduledTimeNoNew time, ISO 8601 with offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (non-destructive, non-idempotent, open-world), and the description adds the lifecycle constraints annotations cannot express: edits apply only to drafts, scheduled-post text edits are gated on a publish-permission key, and time moves for scheduled posts belong to another tool. That is meaningful authorization and state context beyond the structured fields.

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?

Three tight sentences, front-loaded with the editable fields, followed by the exclusion and the prerequisite. No filler and no restatement of the tool name.

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 the mutation's scope, authorization requirement, and the sibling handoff needed to call it correctly, which is strong for a 4-param nested-object tool with no output schema. It stops short of saying what happens to a published post's text or whether an edit resets scheduling/approval state, leaving a modest gap.

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 baseline is 3, but the description adds real semantics: 'overrides' is framed as a network's own caption that takes precedence, and 'scheduledTime' is described as a suggested time only meaningful for drafts. It doesn't add format or bounds detail beyond the schema, which is already complete.

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 (edit/change) and the exact editable fields (caption/body, per-network overrides, suggested time), and scopes them to a DRAFT. It explicitly differentiates itself from reschedule_post and points to list_posts for the id, so an agent can place it among siblings without reading schemas.

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?

Gives explicit when-to-use (DRAFT posts) and when-not-to-use (scheduled posts must go through reschedule_post), plus the extra condition that editing text on an already-scheduled post requires a key the user has allowed to publish. It even names the prerequisite source for postId.

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

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