Skip to main content
Glama

Eurekuh

List connected accounts

list_accounts
Read-onlyIdempotent

The social accounts connected to this organization, with each network's caption limit, image limit and which media types it takes. Posts can only go to a network that appears here, and connecting a new one is a browser flow that no tool can drive.

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_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, open-world read, so the description's job is to add what they can't. It does: it discloses the shape of the returned data (per-network limits and media types) and the hard constraint that account connection is out-of-band and undrivable by any tool, which is genuinely actionable for an agent planning around a missing account.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool returns, followed by the two operational constraints. No filler and nothing repeated from the title or annotations.

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 output schema, the description carries the burden of describing returns, and it does at the field-group level. It's sufficient to call correctly, though it doesn't say whether the list is ever empty or paginated, a minor gap for a per-organization list.

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 parameter is optional with its own description pointing at list_organizations and the default-organization fallback. The description's 'this organization' phrasing is consistent with that but adds no syntax or scoping detail the schema doesn't already carry, so 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?

The description names the resource precisely ('social accounts connected to this organization') and goes beyond the title by enumerating what each entry carries: caption limit, image limit, and accepted media types. It implicitly distinguishes itself from post-related siblings by stating that posts can only target networks appearing here, though it never names an explicit alternative tool.

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?

It gives a clear precondition for downstream use ('posts can only go to a network that appears here'), which tells the agent to call this before composing a post. It also sets a boundary ('connecting a new one is a browser flow that no tool can drive'), heading off a futile search for a connect tool, but it doesn't compare against any named sibling.

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