Skip to main content
Glama

Plaid Get Accounts

plaid_get_accounts
Read-onlyIdempotent

List all linked bank accounts for an access token. Returns account names, types, balances, and masks. Example: get_accounts({ access_token: "access-sandbox-xxx", _apiKey: "client_id:secret" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-plaid-api-key",
      "access_token": "access-sandbox-abc123def456"
    },
    "name": "plaid_get_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesPlaid credentials as "client_id:secret" (e.g. "abc123:def456")
access_tokenYesPlaid access token for the linked institution (access-sandbox-xxx)

Output Schema

NameRequiredDescriptionDefault
itemNoItem metadata
accountsNoList of linked bank accounts
request_idNoUnique request identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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, so the safety profile is covered. The description adds the return payload contents, which is mild added value but largely duplicated by the output schema; it says nothing about token expiry behavior, error modes, or rate limits.

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-loaded with purpose, then return fields, then a compact invocation example — no filler sentences. The example slightly duplicates the input schema's examples block, costing a bit of 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 an output schema present and rich annotations, the description only needs to orient the agent, which it does: what is listed, what comes back, and how to call it. Minor gaps around auth/token lifecycle are acceptable given the structured coverage.

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 access_token and _apiKey are already documented, including the 'client_id:secret' format. The inline example restates the schema's own examples rather than adding new meaning, so the baseline 3 applies.

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?

States a specific verb and resource: 'List all linked bank accounts for an access token,' and enumerates the returned fields (names, types, balances, masks). It does not distinguish itself from the close sibling plaid_get_balance, so an agent must infer the boundary between listing accounts and fetching balance data.

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

Usage Guidelines3/5

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

Usage is only implied — the reader deduces it applies once an institution is linked and an access token exists. There is no statement of when to prefer this over plaid_get_balance or get_transactions, and no prerequisites or failure conditions (expired token, item login required) are given.

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.