Skip to main content
Glama

list_workspaces

Read-onlyIdempotent

List the reeldrop workspaces the connected account belongs to.

Call this first — schedule_reel and every other tool need a workspace_id, and this is how you discover a valid one.

A workspace with timezone="" has never had its scheduling settings configured — get_posting_slots will refuse to compute slots for it, and picking your own default (e.g. UTC, or the account's apparent country) is exactly the kind of guess that produces wrong posting times. Ask the user for their real IANA timezone and call update_scheduling_settings — it's a one-time save, not something to ask on every visit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's value is in the failure mode it discloses: an empty timezone means get_posting_slots will refuse and invented defaults cause wrong posting times. That is real behavioral context an agent could not infer from annotations. It stops short of describing result shape or how many workspaces are typically returned.

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 prerequisite is front-loaded in sentence one and the timezone trap follows in a clearly separated paragraph. The third paragraph is slightly longer than the tool strictly requires, but each sentence carries a distinct instruction (ask the user, use a real IANA value, it is one-time) rather than filler.

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 zero-parameter, read-only list tool with an output schema, nothing needed to call it correctly is missing. The description adds the one thing structure cannot convey: that this call gates the rest of the workflow and what to do when a returned workspace is unconfigured.

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 is 4. The description correctly spends its words on the downstream prerequisite instead of inventing parameter detail.

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 first sentence names a specific verb and resource ("List the reeldrop workspaces the connected account belongs to"), scoped to the connected account. It is distinguishable from siblings like list_ig_accounts or list_automations without opening any schema.

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?

It states explicitly when to call it ("Call this first — schedule_reel and every other tool need a workspace_id") and why: it is the discovery path for a required identifier. It also handles a conditional branch: if timezone is empty, ask the user and use update_scheduling_settings rather than guessing.

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