List User Workspaces
invoke_list_user_workspacesRead-onlyIdempotent
Lists workspaces available to the authenticated user.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Socializioz — AI Social Media Manager
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readiness and safety: readOnlyHint, idempotentHint, and non-destructive false. The description adds 'available to the authenticated user', which gives useful scoping context, but it does not describe the response shape, pagination, or what happens when no workspaces are available.
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?
The description is a single clear sentence with no filler or redundancy. It presents the core function in a directly usable way.
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?
For a zero-parameter read-only list operation with annotations declaring safety, the description is nearly complete. It states a simple, realistic outcome, though it does not mention any output details, which are minor for this simple tool.
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 no parameters, so there are no parameter semantics to explain. The empty schema is fully covered, and the description has no obligation to define nonexistent arguments.
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 uses a specific verb ('Lists') and a specific resource ('workspaces'), and clarifies the scope to the authenticated user. It clearly reads as a list-operation and is distinct from sibling list tools by naming the workspace resource explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to choose this tool over alternatives such as invoke_get_workspace_context or invoke_list_workspace_assets. The description states what the tool does but gives no comparison, exclusion, or situational advice.
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.
TDQS
B3.4/5.0
Disambiguation4/5
Most tools target a distinct resource and lifecycle state, so an agent can usually pick correctly. The main ambiguity is among the profile/context tools and the approve/schedule/publish family, but the descriptions give enough state-specific detail to avoid serious misselection.
Naming Consistency4/5
The set consistently uses an invoke_ prefix with snake_case and mostly follows a verb_noun pattern. It only deviates with names like media_preflight and x_live_read, which place the verb at the end or use noun phrases.
Tool Count2/5
With 33 tools, the server is well beyond the typical well-scoped range. It covers many distinct areas, but the high number of status-specific post tools and separate context/profile/workspace tools makes the surface feel bloated rather than cohesive.
Completeness3/5
The core social publishing workflow is covered well: create, edit, approve, schedule, publish, cancel, retry, and campaign planning. However, there are notable gaps such as no delete/archive for drafts, campaigns, or assets, and limited tools for inbox, comment, or broader analytics beyond the single X read gateway.