Skip to main content
Glama
hermoso-ai

Hermoso

Official

Edit a post on X

edit_x_post

Edit a connected account's X post by replacing its entire text, then get the new post URL to share—editing creates a new ID while the old URL retains the old text. Works within X's one-hour window and reports refusals.

Instructions

EDIT the text of one of the connected account’s own posts on X. Three things about X’s edit model change how you must use this and none is guessable: (1) X REPLACES THE WHOLE TEXT — there is no partial patch, so pass the complete new post; (2) an edit MINTS A NEW POST ID, and the old id keeps resolving and keeps showing the OLD text, so always hand the user the NEW url afterwards or they will circulate a link to the version they just corrected; (3) X’s window is ONE HOUR from the ORIGINAL post and DOES NOT RESTART when a post is edited, and each post has a limited number of edits. Pass whichever id the user has — Hermoso reads X’s edit chain and aims at the newest id, which is the only one X accepts (an edit aimed at the id the user was originally given is refused by X once the post has been edited once). A published ARTICLE can never be edited whatever the subscription, and this says so rather than trying. Editing needs X Premium on the POSTING account; Hermoso attempts it and reports X’s own refusal rather than pre-refusing on a guess about the plan. Everything knowable for free — window closed, edits used up, post ineligible — is refused before anything is billed. Costs credits. Needs X connected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesthe FULL new text of the post. It replaces the old text entirely. Same length rule as a new post: 280 characters, or up to 25,000 on an X Premium account.
postIdYesthe numeric X post id — the last part of the post URL. Any id in the post’s edit chain works; Hermoso resolves the newest one.
Behavior5/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, but the description far exceeds these by detailing behavioral nuances: text replacement, new post ID, edit window, edit limits, Premium requirement, error handling (reports X's refusal), and billing behavior. No contradictions with annotations; adds substantial context beyond structured metadata.

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?

Though lengthy, the description is dense with actionable information, structured with an opening action, numbered key points, and clarifying notes. Every sentence adds value, and critical constraints are front-loaded. It is appropriately sized for the tool's complexity.

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?

The description covers all operational aspects: prerequisites, X-specific edit model, error handling, billing, and the need to return the new URL. It preempts common mistakes and explains edge cases (articles, edit limits). No output schema exists, but the description sufficiently explains expected outcomes and behaviors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions for text and postId, but the description enhances both: text is clarified as the complete replacement (matching the edit model), and postId is enriched with 'Pass whichever id the user has' and explanation of the edit chain resolution. This goes beyond the schema's basic definitions.

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 opens with a specific verb and resource ('EDIT the text of one of the connected account’s own posts on X'), making the tool's purpose unmistakable. It distinguishes itself naturally from siblings like delete_x_post and post_to_x by focusing on editing existing posts and elaborating on the unique constraints of X's edit model.

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?

The description explicitly states when to use the tool (to edit own posts) and provides critical usage rules: whole-text replacement, new post ID creation, one-hour window, limited edits, and ineligibility of articles. It also explains when the tool will attempt versus report refusal, and the need for Premium and X connection, giving clear conditions for invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hermoso-ai/hermoso'

If you have feedback or need assistance with the MCP directory API, please join our Discord server