Skip to main content
Glama

List posting slots

clipember_list_posting_slots
Read-onlyIdempotent

Show the preferred posting times (slots) of the user's accounts: local time, time zone and weekdays. Optionally for one account. A newly connected account starts with 09:00, 13:00, 19:00 every day (starting times the user can change, not a recommendation).

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

Input Schema

NameRequiredDescriptionDefault
connectionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already certify readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fixed. Beyond that, the description discloses the actual payload shape (local time, time zone, weekdays) and a genuinely useful behavioral fact: a newly connected account is pre-seeded with 09:00, 13:00, 19:00 daily, which the agent would otherwise misread as platform-generated recommendations.

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?

Two sentences, front-loaded with the core action and resource, with the default-values caveat as a parenthetical. Tight and readable, though the parenthetical in the second sentence is slightly dense.

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?

A single-optional-parameter read tool with full annotation coverage and no output schema. The description covers the resource, the returned fields, the filter behavior, and the seeded defaults, which is everything an agent needs before calling it.

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?

With one parameter at 0% schema coverage, the schema contributes nothing, so the description must supply all meaning. "Optionally for one account" conveys that omitting it lists every account and supplying it narrows to one, which is the essential semantic, but the description never names the connectionId parameter or indicates it takes an account/connection UUID rather than a handle or name.

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?

States a specific verb and resource ("Show the preferred posting times (slots)") and enumerates exactly what a slot contains – local time, time zone, weekdays. It does not explicitly contrast itself with clipember_add_posting_slot or clipember_delete_posting_slot, but the noun phrase is unambiguous enough that an agent can separate list from mutate on its own.

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?

"Optionally for one account" tells the agent the filtering option exists and that a broad call is the default, and the closing note preempts the misreading that these are recommended times. There is still no explicit statement of when to reach for this versus other listing tools or what to do if the list comes back empty.

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