Skip to main content
Glama

Postemi: Social Media Scheduler

list_groups

Read-onlyIdempotent

Use this when the user manages social channels for several clients or brands and names one: it lists the customer groups the channels are filed under. Pass a group id to list_integrations to see only that client's channels.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral context beyond purpose, such as pagination or rate limits, but output schema and annotations handle the remaining burden. A 3 is appropriate given the strong structured coverage.

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?

Two sentences with zero waste: the first front-loads the usage condition and restates purpose, the second gives the key sibling cross-reference. Every clause earns its place.

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?

Given a simple, parameterless list operation with annotation coverage and an output schema, the description is nearly complete. It could clarify whether groups are returned in a particular order or if there's any pagination, but the output schema likely covers that, making the definition sufficiently complete.

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 has zero parameters, so the schema itself is trivial and the baseline is 4. The description correctly refrains from discussing parameters except to mention a parameter of a sibling tool, which adds no confusion.

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 states a specific verb ('lists') and resource ('customer groups the channels are filed under'), and it directly distinguishes this tool from sibling list_integrations. An agent can tell exactly what it returns and when it applies.

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 explicitly names the scenario: 'Use this when the user manages social channels for several clients or brands and names one.' It also routes to the sibling alternative by saying to pass a group id to list_integrations for filtered results, making the when/how unambiguous.

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.