Skip to main content
Glama

Re-read a channel's metadata

refresh_account

Re-read one connected channel's metadata. On Naver Blog this re-reads the blog's categories through the user's browser extension and waits up to a minute for it; list_accounts then shows the new list under naverBlog.categories. Call this when a category the person mentions is not in list_accounts yet. If the extension is offline you get 202 and the refresh runs when that browser comes back. On Threads, Instagram and Facebook this re-reads the display name and the profile picture. It does not renew a sign-in: a connection whose sign-in the channel has ended answers account_expired, and that account is reconnected on the Connections page. Channels with nothing to re-read return refresh_unsupported. If the response carries bridge, bridge.nextStep says what is needed: run_wake means Chrome with the extension is closed, so tell the person bridge.userMessage with the bridge.wake command for their OS and retry once after they say Chrome is open; ask_user_login / ask_user_update mean tell the person bridge.userMessage. Do not retry more than twice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesThe account id from list_accounts.
workspaceIdNoWhich workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources