Skip to main content
Glama

List your organizations

list_organizations
Read-onlyIdempotent

The organizations you belong to, your role in each and the one these credentials act for Every organization (workspace, in the app) the signed-in person is a member of; with an API key, the member who created it (the key needs organizations:read). type is artist (one artist and its songs), creator (projects: the same records as artists, a performer optional) or label (a roster of artists). current marks the organization these credentials act for. image_url is the picture uploaded for it (null without one); while it has none, image_fallback is the cover of its newest song still there that has one (song_id, preview_url 640 px and thumbnail_url 160 px WebP), to show in its place, or null without such a song. It is read-only, never saved as the picture, and follows the newest song (a new song or an archived one changes it). Each organization has its own plan, music, videos, Looks and credits: to work in another one, sign in again and pick it on the consent screen, or use an API key created in 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. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the bar is lower, and the description still adds real context: the required 'organizations:read' scope, the meaning of the 'current' flag, and the non-obvious derived behavior of image_fallback (it is a live cover from the newest song, never persisted, and changes when songs are added or archived). It does not discuss result size, ordering or pagination, which is the remaining gap.

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

Conciseness2/5

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

The text is a dense run-on with sentence fragments, parenthetical asides and nested clauses ('while it has none, image_fallback is the cover of its newest song still there that has one (song_id, preview_url 640 px and thumbnail_url 160 px WebP)'). Much of the image_url/image_fallback detail is useful in the absence of an output schema, but it is not front-loaded and could be trimmed or bulleted to be scannable.

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 must carry the return shape, and it does: organization type enumeration (artist/creator/label), role, current marker, image fields and their fallback, and the per-organization scoping of plan, music, videos, Looks and credits. Only ordering, pagination and error behavior are absent, which are minor for a small zero-parameter list call.

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 zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The lengthy field documentation is about return values rather than inputs, which is appropriate given no output schema exists.

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 and scope precisely: 'Every organization (workspace, in the app) the signed-in person is a member of', plus the role and the 'current' marker. It is unmistakably distinct from list_artists, list_songs and create_organization. It loses a point only because the leading sentence is a noun fragment rather than a verb+resource statement, and it never explicitly contrasts itself with the other list_* siblings.

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 context is implied rather than stated: the description notes the key needs 'organizations:read' and that acting in another organization requires signing in again and choosing it on the consent screen, or using a key created there. That is a useful workflow hint, but there is no explicit when-to-use/when-not-to-use framing and no named alternative tool for discovering or switching organizations.

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