Skip to main content
Glama

Eurekuh

List organizations

list_organizations
Read-onlyIdempotent

The organizations this connection can act in, with your role and permissions in each. Every other tool takes an optional organizationId (an id from here); leave it out to act in the one marked default. Permissions decide what works there: "post" to upload and create posts, "publish" to go live without approval (without it, scheduled posts wait as pending_approval until someone approves them in the app), "delete" to cancel, "analytics" for stats. The owner can do everything. canPublish false means posts are saved but wait (awaiting_plan) until a plan or the trial starts; trialEndsAt is when the trial ends (null: none); webSubscription is true when a plan bought on the website pays for it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description explains what each permission grants, what happens without publish (pending_approval), what canPublish false implies (awaiting_plan), and the meaning of trialEndsAt and webSubscription. The owner-can-do-everything note and the approval flow are real behavioral context. The permission semantics partly describe other tools' behavior, which is helpful for interpreting the output but not strictly about this call.

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

Conciseness3/5

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

The purpose is front-loaded and every clause carries information. The middle is a dense run-on packed with quoted enum-like values, and the closing flags (canPublish, trialEndsAt, webSubscription) arrive as a comma-spliced list. The content is not wasted, but the structure makes it harder to scan.

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 the description must cover what is returned, and it does: organizations, role, permissions, default marker, canPublish, trialEndsAt, webSubscription. For a no-parameter read tool those are the fields an agent needs in order to reason about permissions later. Nothing material is missing.

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?

This tool takes zero parameters, so there is nothing for the description to clarify about its own input; by the stated baseline that would earn a 4. The organizationId discussion describes how other tools use an id from here, not this tool's parameters. That convention is useful context, but it is not parameter semantics for this call.

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 and what it returns: the organizations the connection can act in, plus the caller's role and permissions in each. That distinguishes it from post/media siblings, which operate inside an organization. It never uses an explicit verb like 'list', so the action is inferred from the name and the phrasing.

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 states clearly that this is the source of the organizationId that every other tool accepts, and what happens when that id is omitted (act in the default organization). That is strong cross-tool routing. It doesn't address when not to call it or how it relates to the similarly named list_accounts.

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