Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage a profile

manage_profile
Destructive

Retrieve, rename, or disconnect social accounts in an Upload-Post profile, and list, select, or clear the default Page used for publishing per network.

Instructions

One Upload-Post profile (username, as list_users returns it). get: the profile and its connected social accounts. rename (display_name): the label shown in the dashboard; the username never changes, so history, schedules and integrations keep working; an empty display_name removes the label. disconnect_social (social_platform: the key in the profile's social_accounts, e.g. instagram): unlinks that one network from the profile; the others stay; reconnecting needs the user to log in to the network again through get_connect_link. Default Page used when publishing, per network (page_type facebook, linkedin or google_business): list_page_choices (every Page or location of the connected account and the one selected), select_page (page_id), clear_page (back to the account's first one). Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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": {
      "action": "<action>",
      "username": "<username>"
    },
    "name": "manage_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
page_idNoselect_page: the Facebook Page id, LinkedIn Page id or Google Business location id from list_page_choices.
usernameYesUpload-Post profile name.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
page_typeNolist_page_choices / select_page / clear_page: which network's Page.
display_nameNorename: the new label; empty or null removes it.
social_platformNodisconnect_social: the network key in the profile's social_accounts, e.g. 'instagram'.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real detail beyond them: it separates the safe `get` action, states that rename preserves history, schedules and integrations because the username is immutable, that disconnect_social leaves other networks intact and requires a fresh login to rejoin, and that clear_page falls back to the account's first Page. The approval/preview protocol (call without `confirmed` to preview, nothing sent, repeat with `confirmed: true` after approval) is a meaningful behavioral disclosure. It stops short of stating permission or rate-limit requirements, so a 4 rather than 5.

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?

Roughly 130 words cover six actions with no filler, and the scoping constraint is front-loaded before the action breakdown. It is delivered as one dense paragraph, so the per-action clauses are harder to scan than a list would be, but every sentence carries information.

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?

An output schema exists, so return shapes need not be explained, and the description correctly stays short on them while covering the prerequisites that matter: user approval before sending, re-login requirements after disconnecting, and the Page-selection prerequisite chain from list_page_choices to select_page. Missing are failure conditions (e.g. what happens when `username` does not exist or a network is not connected), a minor gap given the tool's breadth.

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 coverage is 86%, so the baseline is 3, but the description adds genuine meaning: `display_name` semantics (empty/null removes the label, username never changes), `social_platform` as a key inside social_accounts with an example, `page_type` scoping the three Page actions, and `confirmed` as an approval gate. These go beyond the schema's field-level descriptions rather than restating them.

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 names a specific resource (an Upload-Post profile keyed by `username`) and enumerates every action verb with its effect: get, rename, disconnect_social, list_page_choices, select_page, clear_page. It also distinguishes the resource from siblings, noting `username` is 'as list_users returns it' and that reconnect flows go through `get_connect_link`.

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?

Each action carries an inline use-condition: rename when changing the dashboard label, disconnect_social to unlink one network, list_page_choices/select_page/clear_page to manage the default publishing Page. It names the two relevant siblings with explicit conditions (list_users for the username value, get_connect_link when reconnecting a network), so the agent can route without inference.

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

Deploy Server

Other Tools