Podio MCP Server

List Spaces

podio_list_spaces

Lists all spaces the authenticated user can access in a given organization, returning names and IDs for listing apps. Requires an organization ID.

Instructions

Returns all spaces (workspaces) the authenticated user can access within an organization. Each space includes its name and ID. Use space IDs to list apps.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "org_id": "<org_id>"
    },
    "name": "podio_list_spaces"
  }
}

Input Schema

Name	Required	Description	Default
`org_id`	Yes	Organization ID (from podio_list_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add value by stating the result set is scoped to spaces the authenticated user can access and that each entry carries a name and ID, but it omits pagination, ordering, rate-limit, or permission-failure behavior for a list operation.

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?

Three short sentences, front-loaded with the resource and scope, then the return shape, then the downstream workflow. Every sentence carries information and none is redundant.

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 usefully outlines the return payload (name and ID per space), and the single required parameter is fully covered by the schema. It is close to complete for a simple read-only list tool, missing only pagination/result-size expectations.

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 the single org_id parameter is already documented with its provenance ('from podio_list_organizations'). The description only reinforces that spaces are grouped 'within an organization,' adding no syntax or format detail beyond the schema, 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?

The description names a specific verb+resource ('Returns all spaces (workspaces)') and scopes it to the authenticated user within an organization, which distinguishes it from the app/item siblings. It stops short of explicitly contrasting itself with podio_list_organizations or podio_list_apps, but the resource is unambiguous.

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?

There is no explicit when-to-use statement or when-not-to-use exclusion. Usage is only implied through the workflow hint 'Use space IDs to list apps,' which tells the agent where the output feeds next but not when this tool should be chosen over alternatives.

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