Skip to main content
Glama

Posts: Update post

social_update_post
Destructive

Edit an existing supported social post. Resolve the exact post first, then reuse post.id. Never infer an ID from post text or author. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it.

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": {
      "post_id": "<post_id>"
    },
    "name": "social_update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoReplacement/updated post text requested by the user.
post_idYesExact provider post ID. Resolve/list the post first; never pass post text, author ID or a human description. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
can_commentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / post_id / description
      Previous value: -"Exact provider post ID. Resolve/list the post first; never pass post text, author ID or a human description. Post ID: Exact provider/Unipile post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it."New value: +"Exact provider post ID. Resolve/list the post first; never pass post text, author ID or a human description. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the agent knows this is an irreversible write. The description adds the provider quirk that LinkedIn IDs are preformatted/base64 rather than opaque integers, which is genuinely useful. It does not state required permissions, which post types can or cannot be edited, or what happens to fields left out of the update.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then the ID-resolution rule, then the negative constraint — a sensible ordering with no filler sentences. It loses a point because the "Post ID:" passage duplicates the schema field description almost word for word inside the tool description itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should say what a successful edit returns, and it does not. For a destructive mutation across multiple providers, missing information on which providers/post types are editable and whether omitted fields are preserved leaves real gaps, though the critical ID-safety guidance is covered.

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?

With 75% schema description coverage, the baseline is 3. The description's "Post ID" block is essentially a verbatim repetition of the schema's post_id description, so it adds no new meaning; text and account_id are documented in the schema and can_comment's enum is self-describing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Edit an existing supported social post" gives a specific verb and resource, so an agent can tell this is a cross-provider mutation. However, "supported" is never qualified — the agent cannot tell which providers this covers versus the sibling provider-specific tools like facebook_update_post, linkedin_* and instagram_update_my_profile.

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?

Explicit workflow guidance: resolve the exact post first, reuse post.id, never infer an ID from post text or author, and a clear never-pass list. It also names the resolver tools that yield the ID. What it omits is when to pick this generic tool over a provider-specific update sibling.

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.