Skip to main content
Glama

getWorkspaces

Read-onlyIdempotent

List all workspaces you have access to, with options to filter by type, creator, or API element. Supports pagination and returns visibility status.

Instructions

Gets all workspaces you have access to.

  • For “my …” requests, first call GET `/me` and pass `createdBy={me.user.id}`.

  • This endpoint's response contains the visibility field. Visibility determines who can access the workspace:

    • `personal` — Only you can access the workspace.

    • `team` — All team members can access the workspace.

    • `private` — Only invited team members can access the workspace (Professional and Enterprise).

    • `public` — Everyone can access the workspace.

    • `partner` — Invited team members and partners (Professional and Enterprise).

  • For tools that require the workspace ID, and no workspace ID is provided, ask the user to provide the workspace ID. If the user does not provide the workspace ID, call this first with the createdBy parameter to use the first workspace.

  • Results are paginated. Use the `cursor` parameter to retrieve additional pages.

  • Examples:

    • “List my workspaces” → GET `/me`, then GET `/workspaces?createdBy={me.user.id}&limit=100`

    • “List my personal workspaces” → GET `/me`, then GET `/workspaces?type=personal&createdBy={me.user.id}&limit=100`

    • “List all public workspaces” → GET `/workspaces?type=public&limit=100`

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoThe type of workspace to filter the response by. One of: `personal`, `team`, `private`, `public`, `partner`. - For “my …” requests, this can be combined with `createdBy`. If type is not specified, it will search across all types for that user.
createdByNoReturn only workspaces created by the specified Postman user ID. - For “my …” requests, set `createdBy` to the current user’s ID from GET `/me` (`me.user.id`). - If the user's ID is not known, first call GET `/me`, then retry with `createdBy`.
includeNoInclude the following information in the endpoint's response: - `mocks:deactivated` — Include all deactivated mock servers in the response. - `scim` — Return the SCIM user IDs of the workspace creator and who last modified it.
elementTypeNoFilter results to return the workspace where the given element type is located. If you pass this query parameter, you must also pass the `elementId` query parameter.
elementIdNoFilter results to return the workspace where the given element's ID is located. When filtering by collection, you must use the collection's unique ID (`userId`-`collection`). If you pass this query parameter, you must also pass the `elementType` query parameter.
cursorNoThe cursor to get the next set of results in a paginated response. Get this value from the `meta.nextCursor` field in the previous response.
limitNoThe maximum number of workspaces to return per page. Defaults to 100.
Behavior5/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. The description adds valuable behavioral context: pagination via cursor, visibility field explanation, and the need to call /me for user-specific queries. No contradictions.

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?

The description is longer but well-organized with bullet points and examples. It is front-loaded with the core purpose. Every sentence adds value, though minor trimming could improve conciseness without losing clarity.

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?

For a listing tool with 7 parameters and no output schema, the description covers all aspects: purpose, prerequisites, filtering options, pagination, and visibility. It is complete enough for an agent to use effectively without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds substantial extra context for each parameter: type enum descriptions with usage notes, createdBy with /me integration, include options, elementType/Id coupling, and cursor/lmit explanations. This goes well 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 clearly states 'Gets all workspaces you have access to.' It uses a specific verb and resource, and distinguishes itself from sibling tools like getWorkspace (singular) and createWorkspace.

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?

The description provides explicit guidance: when to call /me first, how to handle missing workspace IDs, pagination, and filtering. It includes examples and alternative approaches, making it easy for the agent to decide when to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/postmanlabs/postman-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server