Blaze

List connected accounts

list_connected_accounts

Read-onlyIdempotent

List the accounts connected to a workspace: social accounts that schedule_posts can publish to, and blog, email, ads, and other integrations. Use it before scheduling to check that each channel will publish.

Each account shows its provider (social providers use the same names schedule_posts accepts), display name, handle when known, account type, status, and when Blaze last checked the connection. Status is "active", "disconnected" (Blaze lost access), or "token expired" (the access token expired and cannot be renewed). Posts to an account that is not active will not publish until it is reconnected in Blaze. Pass provider to list only one provider. Read-only.

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": {
      "workspace_key": "<workspace_key>"
    },
    "name": "list_connected_accounts"
  }
}

Input Schema

Name	Required	Description	Default
`provider`	No	Optional. Only list accounts for this provider, e.g. "instagram" or "linkedin".
`workspace_key`	Yes	Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent, so the bar is lower, but the description goes well beyond them: it defines the three status values, explains the consequence of a non-active account ('Posts to an account that is not active will not publish'), and states the remedy (reconnect in Blaze). That is exactly the operational context an agent needs to interpret results.

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?

Purpose and usage come first, then result fields, then status semantics, then the filter parameter — a sensible front-loaded order. It is on the long side and could compress the field enumeration, but no sentence is redundant.

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?

There is no output schema, so describing the returned fields (provider, display name, handle, account type, status, last-checked time) is necessary and done completely, along with the status enumeration. Nothing an agent needs to call or interpret this tool is missing.

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 100%, so baseline is 3, and the description still adds meaning: 'Pass provider to list only one provider' and the note that social provider names match what schedule_posts accepts, which disambiguates the string values. It does not restate workspace_key, but the schema already documents it thoroughly.

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 and resource ('List the accounts connected to a workspace') and immediately enumerates the account kinds covered. It also names the sibling it pairs with (schedule_posts) and explains the relationship, so an agent can distinguish it from list_workspaces or workspace_info.

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 an explicit trigger: 'Use it before scheduling to check that each channel will publish.' That is a clear when-to-use tied to a concrete workflow. It does not name a when-not-to-use case or a competing alternative, which keeps it just short of a 5.

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

All Blaze 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.