Skip to main content
Glama

List connected accounts

list_connected_accounts
Read-onlyIdempotent

List the user's own accounts connected to Nilyo with provider, owner display name, identifier (LinkedIn public id, phone, email), connection status and reconnection hints. Use when the user asks what is connected, when several accounts of one provider exist and the user names one ("with Julia's LinkedIn"), or after a choose_account result. Nilyo never guesses between accounts: pick the entry matching what the user said and pass its unipile_account_id as account_id to the action tool.

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
providerNoOptional provider filter such as linkedin, whatsapp, instagram, google, outlook or imap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so safety needs no restating; the description instead adds the non-obvious disambiguation policy ('Nilyo never guesses between accounts') and the shape of the returned entries including reconnection hints. It does not discuss ordering, empty-result behavior, or limits, which keeps it just short of a 5.

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?

Three sentences, front-loaded with what is listed before the when-to-use triggers, and each sentence carries distinct information (contents, triggers, disambiguation policy). The parenthetical identifier list is dense but informative rather than padding.

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, and the description compensates by naming the fields returned, which is exactly what an agent needs to pick an entry. It also closes the loop on how the result is consumed (unipile_account_id as account_id), so nothing essential is missing for a read-only list 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 coverage is 100% and the single optional 'provider' filter already lists valid values (linkedin, whatsapp, instagram, google, outlook, imap) in the schema. The description mentions provider only indirectly, via the multi-account scenario, without adding format or matching semantics (exact vs. case-insensitive, prefix matching) beyond the schema.

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?

The description opens with a specific verb and resource ('List the user's own accounts connected to Nilyo') and enumerates the returned fields (provider, owner display name, identifier, connection status, reconnection hints), making the scope unmistakable. An agent can tell this apart from account_connection_status or account_list_attention without opening any schema.

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

Usage Guidelines5/5

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

Three concrete triggering conditions are given: the user asking what is connected, multiple accounts of one provider where the user names one ('with Julia's LinkedIn'), and follow-up after a choose_account result. It also states the forward path explicitly ('pass its unipile_account_id as account_id to the action tool'), so the next call is prescribed rather than inferred.

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.