Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage the Bluesky account

manage_bluesky_account
Destructive

Update a connected Bluesky profile, status, settings, preferences, notifications, chat options, and drafts. Change only the fields you need while leaving other account details unchanged.

Instructions

Change the connected Bluesky account. Fields go in params with the API's names; a field left out stays as it is, and null or clear_fields clears it. update_profile (display_name, description, pronouns, website, avatar_url, banner_url, remove_avatar, remove_banner, pinned_post, links [{url, title}], labels); set_status (status live, url, title, description, duration_minutes) and clear_status; update_settings (chat_allow_incoming all|following|none, chat_allow_group_invites, allow_subscriptions followers|mutuals|none, hide_from_algorithmic_recommendations); update_preferences (preferences: Bluesky preference objects to add or replace; remove / remove_types; replacing a whole list such as muted words or saved feeds, or removing, needs confirm); mark_notifications_seen (seen_at; needs confirm); update_notification_preferences (preferences); set_activity_subscription (subject, post, reply); update_chat_preferences (chat / chat_request: {include all|follows, push}); drafts (text only, no media): create_draft (text, or posts [{text, link_url, quote_uri, labels}] for a thread; langs, reply_settings, quote_settings), update_draft (draft_id), delete_draft (draft_id, needs confirm).

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>",
      "user": "<user>"
    },
    "name": "manage_bluesky_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name with Bluesky connected.
actionYes
paramsNoOther API fields for this action, with the REST API's own names (snake_case) and shapes. See the description for each action's fields. Leave out what you do not want to change.
confirmNoThe API's own confirmation for deletions and other changes that cannot be undone. Set it to true only after the user has approved that exact change; without it those actions are refused and nothing changes.
draft_idNoupdate_draft / delete_draft: the draft id from bluesky_read drafts.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A3.7/5.0
Behavior4/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 safety profile is covered. The description adds real behavior beyond that: omitted fields stay unchanged, null or clear_fields clears a field, and specific actions require `confirm`. It also notes that drafts are text-only with no media, which is useful scoping information.

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

Conciseness3/5

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

The general rule about params, omission, null, and clear_fields is front-loaded well. After that, the description becomes a single run-on enumeration separated by semicolons, which is hard to scan and easy to misread. Every field may earn its place, but the structure does not help the agent parse it.

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?

This is a complex dispatcher with twelve actions, nested objects, and an output schema. The description covers every action name, most relevant fields, and the confirm requirements for irreversible changes, so an agent has enough to choose an action and populate params. It is not fully complete on nested preference shapes or per-field destructive flags, but the output schema and annotations cover the remaining return and safety details.

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 80%, but the `params` object is generic with additionalProperties, so the description carries most of the field-level meaning. It explains that params use the REST API's own names and that omitted fields remain unchanged while null or clear_fields removes them, then enumerates action-specific fields and some enums. The formatting is dense, but it adds substantial meaning beyond the schema.

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?

The first sentence states a specific verb and resource: 'Change the connected Bluesky account.' That clearly separates it from the read-only sibling bluesky_read, though no sibling is named explicitly. The remaining enumeration makes the overall purpose clear but buries it under a wall of field names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb 'Change' and the confirm requirements for irreversible actions. There is no explicit statement that reads should go to bluesky_read or which action to pick for a given user intent. The confirm rules are useful but are behavioral constraints, not routing guidance.

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