Skip to main content
Glama

List my connected accounts

list_connected_accounts
Read-onlyIdempotent

The social accounts connected to PersonaXpand, whether each one works, needs a reconnect, or has part of its inbox off, and whether posting there is possible.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_connected_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description's contribution is telling the agent what per-account health states appear in the result, which is genuinely additive. It stops short of describing pagination, account identity fields, or what a 'part of its inbox off' state means operationally.

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?

One tight sentence with the resource front-loaded and the status enumeration following. No filler or repetition. It is a grammatical fragment rather than a complete sentence, which slightly hurts readability but not economy.

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?

With no input schema, no output schema and simple read-only behavior, the description needs to carry the return semantics — and it does, enumerating the health/status dimensions per account. It would be complete with a brief note on what identifies each account (platform, handle) since no output schema exists to reveal that.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids inventing inputs and instead spends its words on output meaning.

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 description identifies the resource precisely — social accounts connected to PersonaXpand — and adds what each entry conveys (working, needs reconnect, inbox partially off, posting possible). It lacks an explicit verb ('list'), relying on the name to supply it, but an agent can still tell instantly what this returns. No sibling tool competes for this resource, so the absence of differentiation costs little.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives, no prerequisite, and no exclusion. An agent must infer that it is the pre-flight check before posting or before diagnosing why a channel is failing. Usage is implied by the content, not guided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources