flayr

Refresh a connected account's profile

account_refresh

[writes flayr data · write scope] Re-reads a connected account's handle, display name and avatar from the network (use after the user renames the account) and returns the stored values. Changes nothing else: no connect, disconnect or post. If the status is not updated, tell the user to reconnect the account at the returned reconnectUrl. (Wraps POST /api/v2/accounts/{id}/refresh.)

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": {
      "id": "<id>"
    },
    "name": "account_refresh"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	An account id from GET /api/v2/accounts.
`brandId`	No	The brand the account is connected to, as for GET /api/v2/accounts.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds real context beyond the annotations: it declares the `write` scope, states that it writes flayr data but destroys nothing (no connect/disconnect/post), and documents the `status` and `reconnectUrl` outcomes needed to recover from failure. The annotations only give hint flags, so this scope and recovery detail is genuinely additive.

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-loads the scope tag and the core purpose, then packs caveats and the failure path into two tight sentences with the API endpoint as a trailing note. Dense but every clause carries information an agent needs.

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?

With no output schema, the description compensates by describing what is returned (stored handle/display name/avatar, `status`, `reconnectUrl`) and what to do when the refresh fails. Nothing essential to correct invocation is missing for a two-parameter write tool.

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?

Schema description coverage is 100%, so both `id` and `brandId` are already documented in the schema and the description adds no format or constraint detail beyond it. Baseline 3 applies since the schema does the work.

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?

States a specific verb+resource ('Re-reads a connected account's handle, display name and avatar from the network') and explicitly bounds the scope ('Changes nothing else: no connect, disconnect or post'), which separates it from siblings like list_connected_accounts or brand_profile_update.

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?

Gives a concrete trigger condition: 'use after the user renames the account,' plus a follow-up rule when status is not `updated`. It stops short of naming an alternative sibling tool for the other account-management cases, so it is clear context rather than full when/when-not routing.

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

All flayr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?