Skip to main content
Glama

See the whole account: clients, accounts and groups

get_structure
Read-onlyIdempotent

How a Shager account is organized:

  • Organization: the whole account, with one plan and one team. Your key belongs to exactly one organization.

  • Workspaces: inside the organization. In the app a workspace is called a client when the organization is an agency (one workspace per client business) and a brand or simply "my accounts" when a person or business posts for itself (usually one workspace). Everything below lives inside one workspace and never crosses into another.

    • Channels: the connected social accounts of that workspace — one Facebook Page, one Instagram account, one YouTube channel, one X account, one LinkedIn profile or company Page, one TikTok account, one Bluesky account, one Telegram channel, one Mastodon account, one Threads profile, one Pinterest business account, one Tumblr blog, one Google Business Profile location each. A channel belongs to exactly one workspace.

    • Groups: named sets of that workspace's channels (for example "Hebrew pages" or "North branches"). A channel can be in several groups or in none. Targeting a group posts to all of its ACTIVE channels.

    • Media, posts, tracked links, webhooks and the client-approval setting also belong to the workspace.

  • A post belongs to one workspace and targets channel_ids and/or group_ids from that same workspace. Call get_structure (GET /structure) to see the whole tree in one call: every workspace with its channels and groups. When you talk to the person, use their words: "client" (agency) or "your accounts" (one business), and "group".

Returns the organization, then every workspace (client or brand) with its connected channels and its groups (each group lists its channel_ids; each channel lists the groups it is in). Use it before posting to pick the right workspace, channel_ids and group_ids.

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": "get_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the safe-read profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description is free to add domain behavior — and does: group targeting only hits ACTIVE channels, channels may belong to several groups or none, and nothing crosses workspace boundaries. It omits any note on response size or pagination for accounts with many workspaces.

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

Conciseness3/5

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

Well-organized with bullets and front-loaded heading, but the actual instruction to call the tool arrives in the third block after a long hierarchy primer, and the aside about which words to use with the user ("client" vs "your accounts") is helpful terminology rather than invocation guidance. The content is relevant but heavier than a zero-parameter read tool requires.

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?

With no output schema, the description carries the return-shape burden and does so: organization, then each workspace with its channels and groups, each group listing channel_ids and each channel listing its groups. For a no-argument read tool this covers everything needed to call and use it correctly.

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 no parameter meaning to convey; baseline 4 applies. The description correctly focuses its effort on output structure instead.

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?

States a specific verb and resource ("Call get_structure (GET /structure) to see the whole tree in one call: every workspace with its channels and groups") and scopes it against narrower siblings such as list_groups by promising the full hierarchy in one call. An agent can tell exactly what it gets without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit timing guidance: "Use it before posting to pick the right workspace, channel_ids and group_ids," plus the invariant that a post targets channels and groups from the same workspace. It stops short of naming when to prefer a narrower sibling (e.g., list_groups when only groups are needed), so alternatives remain unstated.

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